Objects
JWT Payload
When an end user connects their wallet, you, the developer, get a JSON Web Token (JWT) that can be used to verify some claims about the end user, notably a proof of ownership over a wallet public address.
After authenticating the JWT token, see Server-side verification, you may want to leverage user and wallet information provided in the JWT. Below we have the content defined with the aim of following the JWT standards.
Standard JWT claims:
See: https://www.rfc-editor.org/rfc/rfc7519#section-4.1
Field | Description |
---|---|
aud | Audience for the JWT token. This claim shows what domain of the indended audience of the JWT. |
iss | Issuer of the JWT token. This claim shows app.dynamic.xyz generated and issued the JWT. |
sub | Subject of the JWT token. userId in the deprecated info claim. |
iat | Timestamp when the JWT token was issued. |
exp | Timestamp when the JWT token will expire. |
Dynamic-specific claims:
These fields are optional and you depends on whether you want to collect this information during onboarding. For more information about collecting this information, see here.
alias | Alias field from customer information capture. |
---|---|
Email field from customer information capture. | |
environment_id | Unique ID of the project environment for the SDK, from https://app.dynamic.xyz/dashboard/api. environmentId in the deprecated info claim. |
given_name | First name field from customer information capture. firstName in the deprecated info claim. |
family_name | Last name field from customer information capture. lastName in the deprecated info claim. |
lists | Names of access lists enabled for this user. |
verified_credentials | List of all verified credentials connected to this user. |
verified_account | If present, this was the most recently signed and verified account. |
Example
Was this page helpful?