-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Blocked] Return correct AAL value in user_info JWT #11027
Draft
lmgeorge
wants to merge
6
commits into
main
Choose a base branch
from
lmgeorge/fix-aal-assertion-in-jwt
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
lmgeorge
force-pushed
the
lmgeorge/fix-aal-assertion-in-jwt
branch
2 times, most recently
from
August 7, 2024 16:13
263c27f
to
6d874ee
Compare
zachmargolis
reviewed
Aug 7, 2024
lmgeorge
changed the title
Return correct AAL value in user_info JWT
[DO NOT REVIEW] Return correct AAL value in user_info JWT
Aug 7, 2024
lmgeorge
force-pushed
the
lmgeorge/fix-aal-assertion-in-jwt
branch
from
August 7, 2024 23:54
1172ea4
to
5bb8e3f
Compare
lmgeorge
changed the title
[DO NOT REVIEW] Return correct AAL value in user_info JWT
[Blocked] Return correct AAL value in user_info JWT
Aug 8, 2024
Currently blocked while business rules around how default AAL values should be resolved are formalized. |
lmgeorge
force-pushed
the
lmgeorge/fix-aal-assertion-in-jwt
branch
from
September 4, 2024 16:01
fb45b5c
to
9098ca6
Compare
**Why** * When no AAL ACR value is selected and the SP requires a higher default AAL level or the request demands identity proofing, the user_info block should return the correct AAL ACR value instead of the default AAL ACR * Resolves https://gitlab.login.gov/lg-people/lg-people-appdev/Melba/backlog-fy24/-/issues/55 **How** * Map the ServiceProvider.default_aal value to a known ACR value using a new method (AuthnContextResolver.asserted_aal_value) * Ensure the new asserted AAL ACR value is used as a fallback in the OpenidConnectUserInfoPresenter and OpenidConnectAuthorizeForm so that the JWT built by IdTokenBuilder is correct and doesn't overwrite pre-existing data. changelog: Bug Fixes, OIDC Authentication, Return correct AAL in JWT
lmgeorge
force-pushed
the
lmgeorge/fix-aal-assertion-in-jwt
branch
from
September 16, 2024 20:27
9098ca6
to
3d0070f
Compare
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.
🛠 Summary of changes
Why
How
changelog: Bug Fixes, OIDC Authentication, Return correct AAL in JWT
🎫 Ticket
Link to the relevant ticket: https://gitlab.login.gov/lg-people/lg-people-appdev/Melba/backlog-fy24/-/issues/55
📜 Testing Plan
Provide a checklist of steps to confirm the changes.