The event object for the credentials-exchange Actions trigger provides contextual information about the trigger execution.
event.accessTokenInformation about the access token to be issued. Masquer event.accessToken properties
event.clientInformation about the Client used during this token exchange. Masquer event.client properties
The client id of the application the user is logging in to.
An object for holding other application properties.
The name of the application (as defined in the Dashboard).
event.custom_domainDetails about the custom domain associated with the current transaction. Masquer event.custom_domain properties
Custom domain metadata as key-value pairs.
event.organizationDetails about the Organization associated with the current transaction. Masquer event.organization properties
The Organization identifier.
The friendly name of the Organization.
Metadata associated with the Organization.
The name of the Organization.
event.requestDetails about the request that initiated the transaction. Masquer event.request properties
The body of the POST request. This data will only be available during refresh token, Client Credential Exchange flows and PreUserRegistration Action.
The hostname that is being used for the authentication flow.
The originating IP address of the request.
The language requested by the browser.
The HTTP method used for the request
The value of the User-Agent header received when initiating the transaction.
event.resource_serverInformation about the Resource Server that is issuing the access token. Masquer event.resource_server properties
The identifier of the resource server. For example: https://your-api.example.com.
event.secretsSecret values securely associated with this Action.
event.tenantInformation about the Tenant used during this token exchange. Masquer event.tenant properties
event.transactionInformation about the Credentials Exchange transaction. Masquer event.transaction properties
Correlation ID can be provided in the initial authentication request when the application redirects to Universal Login. You can use value to correlate logs and requests from your Action code with the user flow.
The scopes specified (if any) when requesting the access token.
[Early Access] The live target scope set for the access token. Initialized from the client grants and immediately updated by api.transaction target scope methods across current and subsequent Actions. After all Actions complete, these scopes are intersected with the client grant. Scopes not present in the grant are silently dropped from the final access token.
