Repository navigation
Implementation Advice: consent and authorization screens - #881
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 5b64ae3; 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/429-consent-screens
branch
from
October 28, 2026 13:58
c0e7276 to
7825900
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/434-end-user-errors
branch
from
October 28, 2026 13:58
127bda1 to
a154c89
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/434-end-user-errors
branch
from
November 11, 2026 14:05
a154c89 to
aeef287
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/429-consent-screens
branch
from
November 11, 2026 14:05
7825900 to
579b4e1
Compare
davetonge-mh
commented
Nov 11, 2026
|
|
||
| ## Consent and Authorization Screens | ||
|
|
||
| OpenID Foundation conformance tests do not check that the information shown to the end-user when authorizing access matches the access being granted. Ecosystems should define requirements for this information, particularly where authorization details [@RFC9396] or ecosystem-specific permissions are used, and check them as part of their own certification processes. |
Contributor
Author
There was a problem hiding this comment.
maybe call out the UK customer experience guidelines as an example
davetonge-mh
force-pushed
the
davetonge/impl-advice/434-end-user-errors
branch
from
November 18, 2026 14:01
aeef287 to
b6264a7
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/429-consent-screens
branch
from
November 18, 2026 14:01
579b4e1 to
45778e6
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/429-consent-screens
branch
from
November 18, 2026 14:04
45778e6 to
f166688
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/434-end-user-errors
branch
from
November 18, 2026 14:04
b6264a7 to
eb19309
Compare
FAPI 2.0 asks authorization servers to give end-users the information they need to decide whether to consent, but not how to present it, and conformance tests do not check it. As agreed on #429, ecosystems should define and check it; the UK Customer Experience Guidelines are given as an example. Refs #429
davetonge-mh
force-pushed
the
davetonge/impl-advice/429-consent-screens
branch
from
November 18, 2026 14:11
f166688 to
5b64ae3
Compare
davetonge-mh
force-pushed
the
davetonge/impl-advice/434-end-user-errors
branch
from
November 18, 2026 14:11
eb19309 to
3f7638e
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.
FAPI 2.0 asks authorization servers to give end-users the information they need to decide whether to consent, but does not say how to present it, and conformance tests do not check it. As agreed on the issue, ecosystems should define requirements and check them in their own certification. Following the 11 November call, this adds that context and links the UK Customer Experience Guidelines as an example.
Closes #429