KNOX-3016 - add support for client credentials flow #876
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
smolnar82
reviewed
Mar 11, 2024
...rc/main/java/org/apache/knox/gateway/provider/federation/jwt/filter/JWTFederationFilter.java
Outdated
Show resolved
Hide resolved
.../src/main/java/org/apache/knox/gateway/provider/federation/jwt/filter/AbstractJWTFilter.java
Show resolved
Hide resolved
.../src/main/java/org/apache/knox/gateway/provider/federation/jwt/filter/AbstractJWTFilter.java
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
Adding support for integrations to Knox proxied services and APIs via OAuth style cllient credentials flow. This allows an integration that is provided a CLIENT_ID and CLIENT_SECRET to authenticate to Knox and directly access proxied services with those or exchange those credentials for short lived JWT based access, id and refresh tokens.
This change introduces only the acceptance of the Knox TokenID and Passcode tokens as CLIENT_ID and CLIENT_SECRET in a standard OAuth 2.0 client credentials flow request body. This body will contain the following params:
Authentication using this flow will result in the effective user being what is provided as the CLIENT_ID.
How was this patch tested?
Ran existing tests and added new unit tests
Please review Knox Contributing Process before opening a pull request.