Skip to content

Implementation Advice: consent and authorization screens - #881

Open
davetonge-mh wants to merge 1 commit into
davetonge/impl-advice/434-end-user-errorsfrom
davetonge/impl-advice/429-consent-screens
Open

davetonge-mh wants to merge 1 commit into
davetonge/impl-advice/434-end-user-errorsfrom
davetonge/impl-advice/429-consent-screens

Conversation

@davetonge-mh

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

Copy link
Copy Markdown
Contributor

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

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 5b64ae3; 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/429-consent-screens branch from c0e7276 to 7825900 Compare October 28, 2026 13:58
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/434-end-user-errors branch from 127bda1 to a154c89 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/434-end-user-errors branch from a154c89 to aeef287 Compare November 11, 2026 14:05
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/429-consent-screens branch from 7825900 to 579b4e1 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

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

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.

maybe call out the UK customer experience guidelines as an example

@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/434-end-user-errors branch from aeef287 to b6264a7 Compare November 18, 2026 14:01
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/429-consent-screens branch from 579b4e1 to 45778e6 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/429-consent-screens branch from 45778e6 to f166688 Compare November 18, 2026 14:04
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/434-end-user-errors branch from b6264a7 to eb19309 Compare November 18, 2026 14:04
github-actions Bot pushed a commit that referenced this pull request Nov 18, 2026
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
davetonge-mh force-pushed the davetonge/impl-advice/429-consent-screens branch from f166688 to 5b64ae3 Compare November 18, 2026 14:11
@davetonge-mh
davetonge-mh force-pushed the davetonge/impl-advice/434-end-user-errors branch from eb19309 to 3f7638e 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