Skip to content

Commit 04a3f4b

Browse files
committed
docs(keycloak): clarify incoming mTLS trust scope
The system truststore also verifies HTTPS client certificates unless a separate HTTPS truststore is configured. Operators adding an LDAP CA need to know that this can extend inbound TLS trust as well. Assisted-by: LLM Signed-off-by: Федор Батоногов <[email protected]>
1 parent 8bc8e42 commit 04a3f4b

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

‎packages/system/keycloak/values.yaml‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ extraEnv: []
102102
# name: my-secret
103103
# key: my-key
104104

105-
# Additional trust anchors for outbound TLS (LDAPS, external IdPs, SMTP).
105+
# Additional system trust anchors (LDAPS, external IdPs, SMTP).
106106
# Each entry selects one key from an existing Secret or ConfigMap in the
107107
# release namespace; key defaults to ca.crt. Supply only public certificates:
108108
# PEM bundles or unencrypted PKCS12 (.p12, .pfx, .pkcs12), without private keys.
@@ -111,6 +111,9 @@ extraEnv: []
111111
# The chart reserves the cozystack-* subdirectories there for these mounts.
112112
# These CAs apply to the whole Keycloak server, across all realms, so restrict
113113
# writes to the referenced objects to administrators who manage that trust.
114+
# They also verify incoming client certificates when https-client-auth is
115+
# request or required and no separate https-trust-store-file is configured.
116+
# Set that file explicitly if incoming mTLS needs a different trust boundary.
114117
# Changing an object's contents does not restart Keycloak: restart both pods
115118
# after rotation, or change the referenced object name to trigger a rollout.
116119
# Missing objects/keys prevent the pod from starting. Certificate

0 commit comments

Comments
 (0)