Rename ContextAwareTokenCredential to OidcTokenCredential and move it out of the runtime package #11789
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.
Fixes #10907.
There have been a few queries to do with accessing
RoutingContext
in the customSecurityIdentityAugmentor
.Pedro @pedroigor has already provided a useful
ContextAwareTokenCredential
for the internal (runtime) OIDC purposes.So I've only moved this class to out of the runtime package to make it part of the API, and also renamed it to
OidcTokenCredential
(we may add more properties into it which will be common to both OIDC ID and AccessToken credentials) and renamedgetContext
togetRoutIngContext
and made it public.Stuart, Pedro's original solution looks simple enough for me at the moment and should work, but you may have a better idea how to pass the routing context around, have a look please :-)