RFC 8252: OAuth 2.0 for Native Apps

OAuth 2.0 authorization requests from native apps should only be made through external user-agents, primarily the user's browser. This specification details…

Read RFC 8252 on the RFC Editor

Outgoing relationships (9 related RFCs)

Updates, Normative reference — RFC 6749: The OAuth 2.0 Authorization Framework
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Normative reference — RFC 7595: Guidelines and Registration Procedures for URI Schemes
Normative reference — RFC 7636: Proof Key for Code Exchange by OAuth Public Clients
Informative reference — RFC 6819: OAuth 2.0 Threat Model and Security Considerations
Informative reference — RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol

Incoming relationships (4 related RFCs)

Normatively referenced by — RFC 9700: Best Current Practice for OAuth 2.0 Security
Informatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Informatively referenced by — RFC 9126: OAuth 2.0 Pushed Authorization Requests
Informatively referenced by — RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)