add(considered): browser OAuth architecture is outside the spec scope - #211
Merged
Merged
Conversation
…origin BCP 212 (published 2026-08-21) ranks BFF / token-mediating / browser-only architectures for SPAs using OAuth. Recorded as out-of-scope: where the tokens live is not observable from outside, and the origin-visible parts (cookie attributes, nonce/hash CSP) are already specced. Notes the __Host-Http- prefix as a possible later addition to cookie-attributes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
3d64fd2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://58eefd94.specification-website.pages.dev |
| Branch Preview URL: | https://considered-oauth-browser-bas.specification-website.pages.dev |
jdevalk
changed the title
jdevalk
marked this pull request as ready for review
September 11, 2026 17:13
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
1 participant
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.
Records RFC 10017, OAuth 2.0 for Browser-Based Applications, as
out-of-scope: its central recommendations concern OAuth client architecture. Links the relevant website-level cookie and CSP guidance without suggesting those checks establish compliance with the whole BCP.The summary distinguishes public browser clients from confidential backends. Refresh-token rotation or sender constraint is mandatory for public clients when refresh tokens are issued; it is not a blanket requirement for all three architectures. A BFF keeps tokens out of application JavaScript and authenticates its browser session with a cookie.
The
__Host-Http-cookie prefix remains a possible follow-up for the cookie-attributes page once support is verified.Validation: Astro build, ESLint, formatting, Agent Skill integrity and diff checks pass locally.