This repository has been archived by the owner on Jan 18, 2025. It is now read-only.
Store original encoded and signed identity JWT in OAuth2Credentials #680
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For some authorization flows, including the Auth0 Delegation flow, the endpoint requires the original signed identity JWT to be sent. To support this, it is necessary to store the JWT alongside the decoded content.
This PR adds id_token_jwt as an element in the OAuth2Credentials. It also adds the logic to populate that element in parts of the flows that receive the identity token.
(This is the second PR for this as a previous PR had bad commit email addresses and was closed.)
Resolves: #678