JWT: Difference between revisions
Jump to navigation
Jump to search
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=External= | |||
* https://datatracker.ietf.org/doc/html/rfc7519 | |||
=Internal= | =Internal= | ||
| Line 5: | Line 7: | ||
=Overview= | =Overview= | ||
JSON Web Token (JWT) | 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. | |||
There are a variety of open source libraries available online for creating and signing JWT tokens. See https://JWT.io for more information. | |||
Latest revision as of 17:39, 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.
There are a variety of open source libraries available online for creating and signing JWT tokens. See https://JWT.io for more information.