[WIP] feat(INJI-438): show consent based on api response in QR login flow #933
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
if the response of /v2/authenticate has "consentAction": "CAPTURE", then consent of the user is asked else consent is not asked Signed-off-by: Kiruthika Jeyashankar <[email protected]>
Signed-off-by: Kiruthika Jeyashankar <[email protected]>
Signed-off-by: Kiruthika Jeyashankar <[email protected]>
swatigoel
requested changes
Oct 17, 2023
KiruthikaJeyashankar
changed the title
…-based-on-resp Signed-off-by: Kiruthika Jeyashankar <[email protected] .github.com>
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.
In the QR login flow the consent screen will be displayed as per the response from esignet /linked-authorization/v2/authenticate.