docs: add auth configuration examples to config templates

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: mmartinv

configs/manufacturing.yaml

@@ -21,3 +21,15 @@ device_ca:
 owner:
   cert: "/etc/pki/go-fdo-server/owner-example.crt"
 
+# Authentication and authorization configuration.
+# When enabled, management API endpoints require valid credentials.
+# FDO protocol endpoints (/fdo/101/msg/*, /fdo/200/msg/*) are never affected.
+#auth:
+#  enabled: true
+#  mechanisms:
+#    api_key:
+#      enabled: true
+#  seed:
+#    admin:
+#      name: "admin"
+#      email: "admin@example.com"

configs/owner.yaml

@@ -19,3 +19,15 @@ owner:
   cert: "/etc/pki/go-fdo-server/owner-example.crt"
   key: "/etc/pki/go-fdo-server/owner-example.key"
 
+# Authentication and authorization configuration.
+# When enabled, management API endpoints require valid credentials.
+# FDO protocol endpoints (/fdo/101/msg/*, /fdo/200/msg/*) are never affected.
+#auth:
+#  enabled: true
+#  mechanisms:
+#    api_key:
+#      enabled: true
+#  seed:
+#    admin:
+#      name: "admin"
+#      email: "admin@example.com"

configs/rendezvous.yaml

@@ -49,3 +49,16 @@ rendezvous:
   # allowing the server to start serving requests before running potentially heavy cleanup operations.
   # Default: 300 (5 minutes)
   ##initial_cleanup_delay: 300
+
+# Authentication and authorization configuration.
+# When enabled, management API endpoints require valid credentials.
+# FDO protocol endpoints (/fdo/101/msg/*, /fdo/200/msg/*) are never affected.
+#auth:
+#  enabled: true
+#  mechanisms:
+#    api_key:
+#      enabled: true
+#  seed:
+#    admin:
+#      name: "admin"
+#      email: "admin@example.com"