JSON Web Token
protocol
Overview
Developed byInternet Engineering Task Force
LicenseOpen Standard
Open source✓ Open Source
Use casesecurely transmitting information between parties as JSON object
Technical
Integrates with
Also see
Based onJSON
Knowledge graph stats
Claims47
Avg confidence94%
Avg freshness100%
Last updatedUpdated yesterday
WikidataQ22284678
Trust distribution
100% unverified
Governance
Not assessed
JSON Web Token
concept
Compact URL-safe token format for securely transmitting claims between parties
Compare with...rfc number
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 7519 | ○Unverified | High | Fresh | 1 |
consists of
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| header.payload.signature | ○Unverified | High | Fresh | 1 |
| three Base64-URL encoded parts separated by dots | ○Unverified | High | Fresh | 1 |
standardized by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) | ○Unverified | High | Fresh | 1 |
| IETF | ○Unverified | High | Fresh | 1 |
| IETF | ○Unverified | High | Fresh | 1 |
defined in
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 7519 | ○Unverified | High | Fresh | 1 |
published by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| IETF | ○Unverified | High | Fresh | 1 |
based on
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| JSON | ○Unverified | High | Fresh | 1 |
| JSON Web Encryption | ○Unverified | High | Fresh | 1 |
| JSON Web Signature | ○Unverified | High | Fresh | 1 |
| JSON Web Signature (JWS) | ○Unverified | High | Fresh | 1 |
| JSON Web Encryption (JWE) | ○Unverified | Moderate | Fresh | 1 |
structure consists of
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| header, payload, signature | ○Unverified | High | Fresh | 1 |
governed by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 7519 | ○Unverified | High | Fresh | 1 |
standardized in
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| RFC 7519 | ○Unverified | High | Fresh | 1 |
pricing model
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| free standard | ○Unverified | High | Fresh | 1 |
primary use case
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| securely transmitting information between parties as JSON object | ○Unverified | High | Fresh | 1 |
| compact token format for securely transmitting authentication claims | ○Unverified | High | Fresh | 1 |
| authentication and authorization | ○Unverified | High | Fresh | 1 |
| secure information transmission between parties | ○Unverified | High | Fresh | 1 |
| securely transmitting information between parties as JSON objects | ○Unverified | High | Fresh | 1 |
used by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Auth0 | ○Unverified | High | Fresh | 1 |
first released
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| 2015 | ○Unverified | High | Fresh | 1 |
encoding format
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Base64URL | ○Unverified | High | Fresh | 1 |
authored by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Michael Jones | ○Unverified | High | Fresh | 1 |
| Nat Sakimura | ○Unverified | High | Fresh | 1 |
| John Bradley | ○Unverified | High | Fresh | 1 |
uses format
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Base64URL encoding | ○Unverified | High | Fresh | 1 |
supports protocol
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| OAuth 2.0 | ○Unverified | High | Fresh | 1 |
| OpenID Connect | ○Unverified | High | Fresh | 1 |
| RSA SHA-256 | ○Unverified | High | Fresh | 1 |
| HMAC SHA-256 | ○Unverified | High | Fresh | 1 |
| RSA | ○Unverified | High | Fresh | 1 |
developed by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Internet Engineering Task Force | ○Unverified | High | Fresh | 1 |
| Internet Engineering Task Force (IETF) | ○Unverified | High | Fresh | 1 |
published year
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| 2015 | ○Unverified | High | Fresh | 1 |
integrates with
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| OAuth 2.0 | ○Unverified | High | Fresh | 1 |
| OpenID Connect | ○Unverified | High | Fresh | 1 |
license type
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Open Standard | ○Unverified | High | Fresh | 1 |
implemented by
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Auth0 | ○Unverified | High | Fresh | 1 |
| Firebase Authentication | ○Unverified | Moderate | Fresh | 1 |
alternative to
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| Simple Web Tokens | ○Unverified | Moderate | Fresh | 1 |
| Session cookies | ○Unverified | Moderate | Fresh | 1 |
| SAML tokens | ○Unverified | Moderate | Fresh | 1 |
| Simple Web Tokens (SWT) | ○Unverified | Moderate | Fresh | 1 |
open source
| Value | Trust | Confidence | Freshness | Sources |
|---|---|---|---|---|
| true | ○Unverified | Moderate | Fresh | 1 |