Ato 975/send current credential strength claim to backed #2164
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
isaac-GDS
force-pushed
the
ATO-975/send-current-credential-strength-claim-to-backed
branch
2 times, most recently
from
8ade2e1
to
f7c34ea
Compare
alhcomer
approved these changes
Oct 29, 2024
- Orchestration are sending the currentCredentialStrength claim in the authorize response - update the type and test to show this
- We need to pass the claim `currentCredentialStrength` to the backend and store in the auth session. Passing it from the authorize response to the start handler to be stored.
isaac-GDS
force-pushed
the
ATO-975/send-current-credential-strength-claim-to-backed
branch
from
f7c34ea
to
806b669
Compare
|
isaac-GDS
deleted the
ATO-975/send-current-credential-strength-claim-to-backed
branch
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.
##What
Take the
currentCredentialStrengthfrom the authorise request and pass it on to the start handler so it can be set in the auth session. ThecurrentCredentialStrengthmight not exist in the authorise request and therefore wont pass the field through to the start handler.