JSON Web Token Best Current Practices
RFC 8725
also known as BCP 225
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2023-12-12
|
(System) | Imported membership of rfc8725 in bcp225 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP225 is currently available in the datatracker before this point |
|
2020-02-19
|
(System) | Received changes through RFC Editor sync (created alias RFC 8725, changed abstract to 'JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security … Received changes through RFC Editor sync (created alias RFC 8725, changed abstract to 'JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security tokens that contain a set of claims that can be signed and/or encrypted. JWTs are being widely used and deployed as a simple security token format in numerous protocols and applications, both in the area of digital identity and in other application areas. This Best Current Practices document updates RFC 7519 to provide actionable guidance leading to secure implementation and deployment of JWTs.', changed pages to 13, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2020-02-19, changed IESG state to RFC Published, created updates relation between draft-ietf-oauth-jwt-bcp and RFC 7519, created alias BCP 225) |
|
2020-02-19
|
(System) | RFC published |