[OB3] Fix FAPI 1 advance sub claim inconsistent issue #131
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.
[OB3] Fix FAPI 1 advance sub claim inconsistent issue
This PR fix the id_token's
sub
claim is not consistent in auth flow and token flow. Hence this fails the below test from FAPI 1 Advance suite.Auth flow id token's sub value :
[email protected]@carbon.super
Token flow id token's sub value :
[email protected]
Test name: fapi1-advanced-final
Issue link: https://github.com/wso2-enterprise/ob-compliance-toolkit-uk/issues/474
Doc Issue:
Applicable Labels: Spec, product, version, type (specify requested labels)
Development Checklist
Testing Checklist
Automation Test Details
Conformance Tests Details
Resources
Knowledge Base: https://sites.google.com/wso2.com/open-banking/
Guides: https://sites.google.com/wso2.com/open-banking/developer-guides