メインコンテンツへスキップ

Successful Exchange of Password for Access Token

audience
string
必須

The audience in the JWT associated with the request.

client_name
string
必須

Client name associated with the client_id, when available. May be empty string.

description
string
必須

Description of the event. This can also contain a description of the issue for failure logs.

details
object
必須

Log details

environment_name
string
必須

The name of the environment where the event occurred

:

"prod-eu-1"

"prod-us-1"

ip
必須

The IP address associated with the request. For an auth related log this should be the end user IP. For a machine-to-machine auth flow this should be the IP of the computer doing the authentication. For management logs like sapi and mgmt_api_read this should be the IP of the admin using the manage dashboard.

log_id
string
必須

Log id

tenant_name
string
必須

Tenant name

type
string
必須

Successful Exchange of Password for Access Token

Allowed value: "sepft"
$event_schema
object

Event schema meta

auth0_client

The client or SDK used to do this request, if any. This is based on the Auth0-Client HTTP header.

client_id
string | null

Client related to the API call. Clients are also called applications. The underlying application may not be owned by your tenant and may not be accessible. For failure logs, this may be a valid ID, an invalid one, or any ID.

client_ip

The IP from which we got the request. Note that this does not follow forwarded-for headers unlike the ip field which aims at describing the IP of the end user.

connection
string

Name of the connection, when available. The connection here matches the connection_id field.

connection_id
string

ID of the connection on which the auth flow is happening or connection of the user doing the action, when applicable. For failure logs this field may contain an invalid ID.

date
string

The date when the event occurred in ISO 8601 format

:

"2024-01-15T10:30:00.000Z"

identity_user_id
string

ID for the user as reported by the IdP.

is_mobile
boolean

Whether the request originated from a mobile device. Only present when user_agent is available.

mtls_thumbprint_sha256
string

Representation of the client certificate used to authenticate the client as per RFC 8705 section 3.1. Only included in authorization and token exchanges using mtls as a client authentication method.

scope

List of scopes in the JWT, either as an array like ["read:logs","read:users"] or a space-separated list of scopes like read:logs read:users delete:clients

security_context
object
user_agent
string

The user_agent behind this log, when available

:

"Chrome 120.0.0 / Mac OS X 10.15.7"

user_id
string

ID of the user behind the auth flow, or of the user executing the action, whichever applies. For machine to machine auth flows, this field may contain an empty string. For failure logs, the value may be a valid ID, an invalid ID, or empty string

user_name
string

Username of the user related to the ID is shown in user_id, when available. For failure logs, the value may be a valid username, an invalid username, or empty string.

:
["example@example.com", "+14155554321"]