JWT: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
=External= | |||
* https://datatracker.ietf.org/doc/html/rfc7519 | |||
=Internal= | =Internal= | ||
| Line 8: | Line 10: | ||
JWT defines a compact and self-contained mechanism for transmitting data between parties in a way that can be verified and trusted because it is digitally signed. Additionally, the encoding rules of a JWT also make these tokens very easy to use within the context of HTTP. | JWT defines a compact and self-contained mechanism for transmitting data between parties in a way that can be verified and trusted because it is digitally signed. Additionally, the encoding rules of a JWT also make these tokens very easy to use within the context of HTTP. | ||
JSON Web Token is specified by RFC 7519. | |||
Revision as of 17:37, 3 November 2023
External
Internal
Overview
JSON Web Token (JWT) is an encoding standard for tokens that contain a JSON data payload. The payload can be signed and encrypted.
JWT defines a compact and self-contained mechanism for transmitting data between parties in a way that can be verified and trusted because it is digitally signed. Additionally, the encoding rules of a JWT also make these tokens very easy to use within the context of HTTP.
JSON Web Token is specified by RFC 7519.