Threats, consequences and best practices for single-page and other browser-based applications that use OAuth 2.0, including the backend-for-frontend pattern.
No explainer written for this spec yet. The summary, relations and documented support below are maintained.
Threats, consequences and best practices for single-page and other browser-based applications that use OAuth 2.0, including the backend-for-frontend pattern.
flowchart LR s_browser_based_apps["OAuth 2.0 for Browser-Based Applications"] s_oauth_security_bcp["OAuth 2.0 Security Best Current Practice"] s_oauth2["OAuth 2.0"] style s_browser_based_apps stroke-width:3px s_browser_based_apps -->|Builds on| s_oauth_security_bcp s_browser_based_apps -->|Extends| s_oauth2
Adoption lists only support stated in official documentation (the vendor's or project's own, or a standards body's page naming it), and a weekly check confirms the cited phrase is still on that page. Experimental, alpha and beta support is counted separately as preview.
No sourced support entries collected yet. This says nothing about how widely it is used.
Revisions from the Datatracker, explanations from this site's daily runs, and mailing-list subjects naming the draft.
Nothing collected about this spec yet.