Repository navigation
Implementation Advice: confirming the same end-user - #879
Open
davetonge-mh wants to merge 1 commit into
Open
davetonge-mh wants to merge 1 commit into
davetonge-mh wants to merge 1 commit into
Conversation
|
📄 HTML preview Drafts changed in this PR: Preview of 012291f; updated on every push. For review only — the official specifications are published at https://openid.net/specs/ |
davetonge-mh
force-pushed
the
davetonge/impl-advice/260-native-apps
branch
from
October 28, 2026 13:58
7cc1d0b to
72a7eeb
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/223-same-end-user
branch
from
October 28, 2026 13:58
4ed0bbd to
9e78419
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/223-same-end-user
branch
from
November 11, 2026 14:05
9e78419 to
65766fd
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/260-native-apps
branch
from
November 11, 2026 14:05
72a7eeb to
65bf28c
Compare
davetonge-mh
commented
Nov 11, 2026
|
|
||
| ## Confirming the Same End-User | ||
|
|
||
| OAuth does not identify the end-user to the client, and the FAPI 2.0 Security Profile [@FAPI2_Security_Profile] does not require OpenID Connect. Where a client needs to confirm that the same end-user is authorizing again, for example to extend an existing grant, it can use OpenID Connect and request the `sub` claim in the ID Token with the expected value using the `claims` parameter, as described in Section 5.5.1 of [@OIDC]. The authorization server then only returns a successful response for that end-user. |
Contributor
Author
There was a problem hiding this comment.
id_token_hint as a better option, claims param not always supported
davetonge-mh
force-pushed
the
davetonge/impl-advice/223-same-end-user
branch
from
November 18, 2026 14:01
65766fd to
c8bb8dc
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/260-native-apps
branch
from
November 18, 2026 14:01
65bf28c to
c6f6849
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/260-native-apps
branch
from
November 18, 2026 14:04
c6f6849 to
ec29467
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/223-same-end-user
branch
from
November 18, 2026 14:04
c8bb8dc to
39bc6e2
Compare
Send id_token_hint or request the expected sub value using the claims parameter, then check sub in the returned ID Token. This relies on sub being stable, so where an ecosystem allows sub to change on each authorization, for example to a consent identifier, OpenID Connect cannot be used to identify end-users. Refs #223
davetonge-mh
force-pushed
the
davetonge/impl-advice/223-same-end-user
branch
from
November 18, 2026 14:11
39bc6e2 to
012291f
Compare
This branch has not been deployed
This file contains hidden or 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
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.
OAuth does not identify the end-user to the client, and FAPI 2.0 does not require OpenID Connect. Where a client needs to confirm that the same end-user is authorizing again, it can send
id_token_hintor request the expectedsubvalue using theclaimsparameter (OIDC Core 3.1.2.2), then checksubin the returned ID Token. A note says that authorization servers do not have to supportclaimsor accept an expired ID Token as a hint.This relies on a stable
sub(OIDC Core 5.7). Where an ecosystem allowssubto change on each authorization, for example to a consent identifier as reported on the issue, OpenID Connect cannot be used to identify end-users. Ecosystems that need this should require a stablesub, which can be pairwise (OIDC Core 8).Closes #223