feat: support custom jwt assertion claim #1400
Closed
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
|
Closing this PR and re-creating it from a branch in the NUWCDIVNPT repo instead of my personal fork. |
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.
Resolves #1399
The PR adds support in the API for a user provided OAuth2 claim that fulfills the role of an Assertion ID. The default value
jtican be overridden using the envvarSTIGMAN_JWT_ASSERTION_CLAIM. The API updates a User'slastClaimsproperty when presented with a JWT for the User where the Assertion ID claim's value differs from the value of that claim inlastClaims.Includes updates and some rewording of the Documentation.
Also updates the
cookiemodule from 0.6.0 to 0.7.1 to resolve an NPM audit failure.