Signed JWT Tokens

The response to authentication will be signed JWT tokens. Once you validate and decode them you get data that is shown in the following examples.

The JWT payload will include the provisioned credential id and session identifier.

{
  "exp": 1703577870,
  "nbf": 1703577570,
  "iat": 1703577570,
  "auth_time": 1703577570,
  "jti": "f4fefc31-6d69-40b8-a0be-683359c9e9d7",
  "iss": "https://{environment-url}/realms/{partner-id}",
  "sub": "10d712a2-66b2-4979-92ba-b09f04d303bd",
  "typ": "Bearer",
  "azp": "api",
  "session_state": "4da1b517-6491-448a-9edf-efe8ad0d1668",
  "scope": "",
  "sid": "4da1b517-6491-448a-9edf-efe8ad0d1668",
  "session_identifier": "WSqNfqbYgTg",
  "type": "otp",
  "credential_id": "64707473-47ff-4dae-977d-0e16eabc2150"
}

Parameters

• sid : Transaction ID for the purpose of reconciliation.

• session_identifier: A unique identifier for this particular session or operation.

• type: The type of operation performed, which in this context is "otp".

• credential_id: The credential id provisioned for the user for the future authentications