Technology and engineering · 2017
RFC 8252: OAuth 2.0 for Native Apps
by W. Denniss, J. Bradley
OAuth 2.0 authorization requests from native apps should only be made through external user-agents, primarily the user's browser. This specification details the security and usability reasons why this is the case and how native apps and authorization servers can implement this best practice.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2017
- Status
- Best Current Practice
- Pages
- 21
- Updates
- RFC 6749
- Also known as
- BCP 212
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.