RANGER-5795: Support pluggable token supplier in Ranger REST client to obtain and refresh bearer tokens dynamically - #1227
Open
kumaab wants to merge 3 commits into
Open
RANGER-5795: Support pluggable token supplier in Ranger REST client to obtain and refresh bearer tokens dynamically#1227kumaab wants to merge 3 commits into
kumaab wants to merge 3 commits into
Conversation
…o obtain and refresh bearer tokens dynamically
nixonrodrigues
approved these changes
Sep 11, 2026
kumaab
marked this pull request as draft
September 11, 2026 21:47
kumaab
marked this pull request as ready for review
September 13, 2026 18:11
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.
What changes were proposed in this pull request?
Introduce new config:
ranger.plugin.<service>.policy.rest.client.jwt.supplierto supply a custom Token SupplierDefaultTokenSupplierif unavailable andJWT_SOURCEis configured.The configured class must implement the JDK's
java.util.function.Supplier<String>, so custom token suppliers can be plain lambdas/suppliers with no dependency on Ranger libraries. If the property is set, the class is instantiated via reflection.Refactoring occurrences to generic TokenSupplier and using JWT as one default implementation via
DefaultTokenSupplierHow was this patch tested?