OAuth 2.0 for Native Apps
RFC 8252
also known as BCP 212
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2024-01-25
|
(System) | Received changes through RFC Editor sync (removed Errata tag (all errata rejected)) |
|
2023-12-12
|
(System) | Imported membership of rfc8252 in bcp212 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP212 is currently available in the datatracker before this point |
|
2022-08-16
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2020-07-29
|
(System) | Received changes through RFC Editor sync (removed Errata tag (all errata rejected)) |
|
2019-08-28
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2019-07-11
|
(System) | Received changes through RFC Editor sync (removed Errata tag) |
|
2019-07-09
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2017-10-04
|
(System) | Received changes through RFC Editor sync (created alias RFC 8252, changed abstract to 'OAuth 2.0 authorization requests from native apps should only be made … Received changes through RFC Editor sync (created alias RFC 8252, changed abstract to '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.', changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2017-10-04, changed IESG state to RFC Published, created updates relation between draft-ietf-oauth-native-apps and RFC 6749, created alias BCP 212) |
|
2017-10-04
|
(System) | RFC published |