Translate access token instead of id token to gRPC backend in Flyte Admin HTTP middleware #5979
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.
Tracking issue
Closes #5978
Why are the changes needed?
See #5978
What changes were proposed in this pull request?
HTTP middleware translates session cookies into gRPC metadata containing the access token as opposed to the id token
Note: This has a subtle side effect that with blanket authorization the access token must include the
all
scope.How was this patch tested?
Unit tests
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link