Add SASL EXTERNAL authentication for LDAP federation using Java default keystore - #48879
Draft
tsaarni wants to merge 1 commit into
Draft
Add SASL EXTERNAL authentication for LDAP federation using Java default keystore#48879tsaarni wants to merge 1 commit into
tsaarni wants to merge 1 commit into
Conversation
This was referenced May 11, 2026
Signed-off-by: Tero Saarni <tero.saarni@est.tech>
tsaarni
force-pushed
the
mutual-tls-for-ldap2
branch
from
May 11, 2026 11:53
0cc51da to
a8c8029
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This is PoC for SASL EXTERNAL client certificate authentication for LDAP federation using Java default keystore
This change adds support for SASL EXTERNAL method, using x509 certificate as client credentials for LDAP federation. It works with both: LDAPS and LDAP + StartTLS.
This is much simplified successor of #7365. It replaces the custom KeyStore SPI proposal with the default Java KeyStore using
javax.net.ssl.keyStoreandjavax.net.ssl.keyStorePasswordproperties. Although this approach was previously rejected (link) it was long time ago and things might have changed since then (see #7365 (comment) which might have referred to #29654 (comment)).KeyStore hot-reloading is supported without a server restart. Please note that PEM files for client certificates and keys are not supported, nor is the truststore SPI. For trusted certificates, use
KC_TRUSTSTORE_PATHS(link).See also #48832 for another PoC which uses Quarkus TLS registry for the same goal.
Fixes #11725