Skip to content

keycloak: no way to add a private CA to the truststore (LDAPS, external IdP, SMTP) #3823

Closed

Description

The system Keycloak has no way to trust a private CA, so any outbound TLS it initiates against an internal endpoint fails. The case that raised it in the community chat is an LDAPS user federation backed by an organisation's own CA; the same wall stands in front of an external OIDC identity provider or an SMTP server with an internal certificate.

Upstream handles this without ceremony: certificates dropped into conf/truststores are picked up automatically, as PEM or unencrypted PKCS12, and KC_TRUSTSTORE_PATHS points elsewhere if needed.

Our chart cannot deliver the file. packages/system/keycloak/templates/sts.yaml mounts only the themes volume and carries no extraVolumes or extraVolumeMounts, so there is no supported way to place a CA bundle into the container. Patching the StatefulSet by hand does not survive, Flux reconciles it back.

What would close it: a values field taking a Secret or ConfigMap reference, mounted read-only at /opt/keycloak/conf/truststores. No env var needed since Keycloak scans that directory on its own.

Raised here: https://t.me/cozystack_ru/12472

Activity

  1. added
    triage/acceptedIndicates an issue is ready to be actively worked on
    priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Sep 23, 2026
  2. added a commit that references this issue on Oct 26, 2026
    7215b02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/keycloakIssues or PRs related to Keycloak (SSO / identity)kind/featureCategorizes issue or PR as related to a new featurepriority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to completetriage/acceptedIndicates an issue is ready to be actively worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions