Inspect Claims in ID Token

An ID Token is a JSON Web Token (JWT) containing cryptographically signed claims about a user's profile information. This is issued by Scalekit after successful authentication. The ID Token is a Base64-encoded JSON object with three parts: header, payload, and signature.

Here's an example of the payload. Note this is formatted for readability and the header and signature fields are skipped.

Sample Payload

Loading...

Full list of ID Token Claims

Claim	Presence	Description
aud	Always	Intended audience (client ID)
amr	Always	Authentication Method Reference values
exp	Always	Expiration time (Unix timestamp)
iat	Always	Issuance time (Unix timestamp)
iss	Always	Issuer identifier (Scalekit environment URL)
oid	Always	Organization ID of the user
sub	Always	Subject identifier for the user
at_hash	Always	Access token hash
c_hash	Always	Authorization code hash
azp	Always	Authorized presenter (usually same as aud)
email	Always	User's email address
email_verified	Optional	Email verification status
name	Optional	User's full name
family_name	Optional	User's surname or last name
given_name	Optional	User's given name or first name
locale	Optional	User's locale (BCP 47 language tag)
picture	Optional	URL of user's profile picture

Usage Notes

1. The ID Token is received over a secure HTTPS channel using the client secret.
2. Validation of the ID Token is handled automatically when using the Scalekit SDK.
3. The sub claim combines the connection_id and the provider's unique identifier.
4. The iss claim must match your Scalekit environment URL.
5. The amr claim typically contains the connection_id used for authentication.

This structure provides a neutral, factual reference for ID Token Claims in Scalekit, organized according to the data structure itself.

An ID Token is nothing but a cryptographically signed Base64-encoded JSON object containing a set of name/value pairs about the user's profile information. Essentially, it is a JWT token. Ideally, it is advised that you validate an ID token before you use it, but since you are communicating directly with Scalekit over an intermediary-free HTTPS channel and using your client secret to exchange the code for the ID Token, you can be confident that the token you receive really comes from Scalekit and is valid.

If you are using our Scalekit SDK to exchange the code for the ID Token, the work of decoding the base64url-encoded values and parsing the JSON within, validating the JWT and accessing the claims within the ID token is automatically taken care of.