This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
Add JWT auth to Keycloak #217
Open
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hello,
I'm creating this PR related to my Issue #201.
If the value of <<__enable_jwt__auth>>=True the oauth2-proxy will authenticate requests with the bearer token instead of the oauth2_proxy cookie, to enable m2m authentication.
To make this happen you need to create a new client in Keycloak and enable direct auth.
Any Suggestions or doubts? I'm happy to hear your sights. @karlschriek @davidspek