Skip to content

Implementation Advice: confirming the same end-user - #879

Open
davetonge-mh wants to merge 1 commit into
davetonge/impl-advice/260-native-appsfrom
davetonge/impl-advice/223-same-end-user
Open

davetonge-mh wants to merge 1 commit into
davetonge/impl-advice/260-native-appsfrom
davetonge/impl-advice/223-same-end-user

Conversation

@davetonge-mh

@davetonge-mh davetonge-mh commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

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_hint or request the expected sub value using the claims parameter (OIDC Core 3.1.2.2), then check sub in the returned ID Token. A note says that authorization servers do not have to support claims or accept an expired ID Token as a hint.

This relies on a stable sub (OIDC Core 5.7). Where an ecosystem allows sub to 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 stable sub, which can be pairwise (OIDC Core 8).

Closes #223

github-actions Bot pushed a commit that referenced this pull request Oct 28, 2026
@github-actions

github-actions Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

📄 HTML preview

Drafts changed in this PR:

All drafts

Preview of 012291f; updated on every push. For review only — the official specifications are published at https://openid.net/specs/

@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/260-native-apps branch from 7cc1d0b to 72a7eeb Compare October 28, 2026 13:58
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/223-same-end-user branch from 4ed0bbd to 9e78419 Compare October 28, 2026 13:58
github-actions Bot pushed a commit that referenced this pull request Oct 28, 2026
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/223-same-end-user branch from 9e78419 to 65766fd Compare November 11, 2026 14:05
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/260-native-apps branch from 72a7eeb to 65bf28c Compare November 11, 2026 14:05
github-actions Bot pushed a commit that referenced this pull request Nov 11, 2026
Comment thread FAPI_2_0_Implementation_Advice.md Outdated

## 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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

id_token_hint as a better option, claims param not always supported

@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/223-same-end-user branch from 65766fd to c8bb8dc Compare November 18, 2026 14:01
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/260-native-apps branch from 65bf28c to c6f6849 Compare November 18, 2026 14:01
github-actions Bot pushed a commit that referenced this pull request Nov 18, 2026
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/260-native-apps branch from c6f6849 to ec29467 Compare November 18, 2026 14:04
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/223-same-end-user branch from c8bb8dc to 39bc6e2 Compare November 18, 2026 14:04
github-actions Bot pushed a commit that referenced this pull request Nov 18, 2026
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
davetonge-mh force-pushed the davetonge/impl-advice/223-same-end-user branch from 39bc6e2 to 012291f Compare November 18, 2026 14:11
github-actions Bot pushed a commit that referenced this pull request Nov 18, 2026

This branch has not been deployed

No deployments
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 this pull request may close these issues.

1 participant