Option to allow the OIDC id_token to be stored in cookie and used as principal #3552
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
…principal token (cherry picked from commit 1e97e2f)
|
Hello, this conflicts with existing PR: #3456 |
Sorry I didn't realize the logout PR covered this. It doesn't cover the use case of using it as the Principal though. Would you be open to integrating that portion into your PR? I could assist if needed. |
|
Closing due to conflict, will add ability to use id token as principal with changes in #3456 |
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.
Some OIDC providers don't return the actual profile in the access_token. This option will allow the id_token from the token endpoint to be stored in the cookie and utilized to build the principal for use in context.