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.
IETF · RFCОфициальная английская аннотация
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.
{
"id": "RFC8725",
"number": 8725,
"title_en": "JSON Web Token Best Current Practices",
"title_ru": "",
"summary_ru": "",
"purpose_ru": "",
"use_ru": "",
"full_translation_path": "",
"full_translation_checked_at": "",
"full_translation_source_sha256": "",
"architect_note_ru": "",
"topics_ru": [],
"translation_state": "not_prepared",
"verification_level": "not_prepared",
"verification_level_ru": "Русская выжимка не подготовлена",
"verification_note_ru": "",
"abstract_en": "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.",
"authors": [
"Y. Sheffer",
"D. Hardt",
"M. Jones"
],
"organizations": [],
"publication_date": "2020-02-01",
"current_status": "BEST CURRENT PRACTICE",
"current_status_ru": "Лучшая современная практика",
"publication_status": "BEST CURRENT PRACTICE",
"publication_status_ru": "Лучшая современная практика",
"lifecycle": "active",
"lifecycle_ru": "Действующий",
"stream": "IETF",
"stream_ru": "IETF",
"area": "sec",
"area_ru": "Безопасность",
"working_group": "oauth",
"source_draft": "draft-ietf-oauth-jwt-bcp-07",
"page_count": 13,
"doi": "10.17487/RFC8725",
"keywords": [
"JSON Web Token",
"JWT",
"JSON Object Signing and Encryption",
"JOSE",
"JSON Web Signature",
"JWS",
"JSON Web Encryption",
"JWE",
"attacks",
"Claims",
"Security",
"Cryptography"
],
"formats": [
"HTML",
"TXT",
"PDF",
"XML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [
"RFC7519"
],
"updated_by": [],
"is_also": [
"BCP225"
],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc8725/",
"html": "https://www.rfc-editor.org/rfc/rfc8725.html",
"txt": "https://www.rfc-editor.org/rfc/rfc8725.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc8725/"
}
}