JSON Web Tokens (JWT)

E192655

authentication mechanism open standard token format

JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (11)

Label	Occurrences
JSON Web Token	12
JWT	6
JSON Web Tokens	2
IAP-Signed JWT	1
JSON Web Token (JWT)	1
JSON Web Token Profile for OAuth 2.0 Access Tokens	1
JSON Web Tokens (JWT) canonical	1
JWT (JSON Web Token)	1
JWT (JSON Web Tokens)	1
JWT SVID	1
MicroProfile JWT Authentication	1

How this entity was disambiguated

This entity first appeared as the object of triple T1711792 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: JSON Web Tokens (JWT)
Context triple: [HMAC, usedFor, JSON Web Tokens (JWT)]

A. RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
B. OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
C. RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
D. OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
E. JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: JSON Web Tokens (JWT)
Target entity description: JSON Web Tokens (JWT) are a compact, URL-safe standard for securely transmitting digitally signed claims between parties, commonly used for stateless authentication and authorization in web applications.

A. RFC 6750
RFC 6750 is an IETF specification that defines the use of bearer tokens for securing HTTP requests in the OAuth 2.0 authorization framework.
B. OpenID Connect
OpenID Connect is an identity layer built on top of OAuth 2.0 that enables secure user authentication and single sign-on across applications.
C. RFC 6749
RFC 6749 is the IETF specification that defines the OAuth 2.0 authorization framework used for secure delegated access to web resources.
D. OAuth 2.0
OAuth 2.0 is an industry-standard authorization framework that enables applications to obtain limited access to user resources on HTTP services without exposing user credentials.
E. JSON
JSON (JavaScript Object Notation) is a lightweight, text-based data interchange format widely used for transmitting structured data in web APIs and configuration files.
F. None of above. chosen

Statements (64)

Predicate	Object
instanceOf	authentication mechanism ⓘ open standard ⓘ token format ⓘ
abbreviation	JWT ⓘ linked to: JSON Web Tokens (JWT)
canBeEncryptedUsing	JWE ⓘ
commonlyTransportedIn	HTTP Authorization header ⓘ HTTP cookies ⓘ URL query parameters ⓘ
commonlyUsedWith	OAuth 2.0 ⓘ OpenID Connect ⓘ
component	header ⓘ payload ⓘ signature ⓘ
definedIn	RFC 7519 ⓘ
designGoal	interoperability ⓘ scalability ⓘ statelessness ⓘ
doesNotProvideByDefault	confidentiality ⓘ
enables	bearer token authentication ⓘ
encodedWith	Base64url ⓘ
headerField	alg ⓘ typ ⓘ
is	URL-safe ⓘ compact ⓘ
payloadField	aud ⓘ exp ⓘ iat ⓘ iss ⓘ jti ⓘ nbf ⓘ sub ⓘ
primaryUse	authorization ⓘ stateless authentication ⓘ
relatedStandard	JOSE ⓘ JWE ⓘ JWS ⓘ
requires	audience validation ⓘ expiration validation ⓘ secure key management ⓘ
risk	improper validation ⓘ signature algorithm confusion ⓘ token theft ⓘ
securityProperty	authenticity ⓘ integrity ⓘ
signatureAlgorithmType	ECDSA ⓘ linked to: Elliptic Curve Digital Signature Algorithm HMAC ⓘ RSA ⓘ
standardizedBy	IETF ⓘ linked to: Internet Engineering Task Force
supports	digitally signed claims ⓘ integrity protection ⓘ optional encryption ⓘ stateless session management ⓘ
supportsAlgorithmFamily	ES256 ⓘ HS256 ⓘ RS256 ⓘ
supportsUseCase	ID tokens ⓘ access tokens ⓘ refresh tokens ⓘ
transmits	claims ⓘ
typicalStructure	header.payload.signature ⓘ
usedIn	microservices architectures ⓘ single-page applications ⓘ web applications ⓘ
usesDataFormat	JSON ⓘ

How these facts were elicited