feat(sdk): expose AccessTokenSource #1928
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 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.
Proposed Changes
Expose
AccessTokenSourcefrom SDK instance.This would allow me to reuse an existing
IDPTokenExchangeTokenSourceinstance.Context
I'm retrieving the entitlements for a user while using the
ClaimsEntityResolutionService.For that I'm retrieving an
EntityChainviaclient.EntityResoution.CreateEntityChainFromJwtand pass that toclient.Authorization.GetEntitlements.I would like to avoid implementing the token exchange myself when there's already an implementation available through the sdk. Unfortunately it's a bit cumbersome to setup, so I would like to reuse the existing instance from the sdk, which currently is not exposed.
Checklist
Testing Instructions