vulns.co
/
GKData.io MCP and API Buy me a coffee

Internet Engineering Task Force / RFC Editor

RFC 10017: OAuth 2.0 for Browser-Based Applications

RFC 10017 compares browser-only OAuth clients, token-mediating backends and backend-for-frontend designs by where they keep tokens and manage sessions. It distinguishes protecting token material from limiting what compromised application code on the same origin can still do.

Open the referenceTechnical StandardReviewed 2026-10-03

How to use this reference

Document which component holds each credential, binds the user session, and enforces request destinations. Compare those responsibilities and residual risks against an owned application’s architecture.

Before reading

  • OAuth client and resource-server roles
  • Browser origins, cookies, and HTTP redirects

Context and limits

  • Backend token custody does not make compromised application code harmless.
  • Browser-specific guidance complements RFC 9700; it does not establish security of a particular deployment.

Sources

  1. RFC 10017: OAuth 2.0 for Browser-Based ApplicationsInternet Engineering Task Force / RFC Editor · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software