Add SASL EXTERNAL authentication for LDAP federation using TLS Registry#48832
Draft
tsaarni wants to merge 1 commit intokeycloak:mainfrom
Draft
Add SASL EXTERNAL authentication for LDAP federation using TLS Registry#48832tsaarni wants to merge 1 commit intokeycloak:mainfrom
tsaarni wants to merge 1 commit intokeycloak:mainfrom
Conversation
Signed-off-by: Tero Saarni <tero.saarni@est.tech>
70e13e8 to
a3a37c4
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
1 participant
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 Quarkus TLS registry.
#7365 (comment)
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, replacing the custom KeyStore SPI proposal with the Quarkus TLS Registry which includes similar functionality and much more. As there is no prior precedent for using the TLS registry inKeycloak, configuration happens at the Quarkus level. Example via environment variables:
For trusted certificate KC_TRUSTSTORE_PATHS is used: