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

Inclusion of the "user" field in a modification #93

Closed
jricher opened this issue Nov 13, 2020 · 2 comments · Fixed by #427
Closed

Inclusion of the "user" field in a modification #93

jricher opened this issue Nov 13, 2020 · 2 comments · Fixed by #427
Assignees

Comments

@jricher
Copy link
Collaborator

jricher commented Nov 13, 2020

§5.3 Modifying an Existing Request: Editor's note:

This would allow the client to do things like gather the user's identifiers post-request, or gather an assertion from an on-device element that the AS can verify. It opens up potential avenues for trouble if the user here is different from the RO that's already showed up at the AS or race conditions if the RQ's identity changes mid-stream. But that said, this seems important for multi-log-in cases and the like, probably.

@fimbault
Copy link
Collaborator

We could include a warning, saying that the AS should check that it is indeed the same user, typically through validating the sub_id

@yaronf
Copy link
Contributor

yaronf commented Jul 1, 2022

We could include a warning, saying that the AS should check that it is indeed the same user, typically through validating the sub_id

Please make it normative.

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.

3 participants