docs: document auth configuration in server config templates

Add a commented auth section to all three server config templates
(manufacturing, owner, rendezvous) showing how to enable API key
authentication and seed an initial admin user. Notes that FDO protocol
endpoints are never affected by management API auth.

Signed-off-by: Miguel Martín <mmartinv@redhat.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"