Skip to content
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

sub attribute meaning & cardinality #29

Closed
bigludo7 opened this issue Mar 17, 2023 · 2 comments
Closed

sub attribute meaning & cardinality #29

bigludo7 opened this issue Mar 17, 2023 · 2 comments
Assignees

Comments

@bigludo7
Copy link
Collaborator

@DT-DawidWroblewski another point...

sub attribute should probably be defined in the API documentation/swagger.
I understood this is an uuid to identified the 'transaction' but this need to be clarified

Another point on this sub - as it is not clearly mentioned in IDY.54 is it fair to tag it as mandatory in the response? In Orange implem for example we do not manage it.

Thanks.

@DT-DawidWroblewski
Copy link
Collaborator

Hi @bigludo7 !

I (once again ;) ) reviewed MC specs for this purpose.

Sub is a mandatory artifact of MC resource response, as it binds token response (ID Token "sub" field) with resource response.

For reference, please see IDY.03, article 6.2

The “sub” (subject) claim containing the PCR MUST always be returned in the Resource Response so that the Resource Response is tied with the ID Token and the User in this context. This allows the SP to validate the response.

@DT-DawidWroblewski
Copy link
Collaborator

MC cleared

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants