Event attributes
Every event carries a number of attributes that document various aspects of the event. The event attributes are structured in the following categories:
Event attributes | Description |
---|---|
The core information provided by an event. | |
A unique identifier for the event. | |
Information on the event producer. | |
Information about the request that caused the event to be triggered. |
Event object data
Event object data are the core information provided by an event. All end-user notification events have in common that they provide the username concerned by the event as well as additional information depending on the concrete use case. This could for example be a device ID, when an Airlock 2FA device is activated, or the reason why a user has been locked.
A full list of all events including their event data is listed below:
Event | Description | Event Data | ||
---|---|---|---|---|
Attribute | Description | Example | ||
Airlock 2FA Device Activated | User activated a new Airlock 2FA device |
| Username concerned by the event |
|
| User's Airlock 2FA account ID |
| ||
| ID of activated Airlock 2FA device |
| ||
Airlock 2FA Device Deleted | An Airlock 2FA device was deleted |
| Username concerned by the event |
|
| User's Airlock 2FA account ID |
| ||
| ID of deleted Airlock 2FA device |
| ||
Airlock 2FA Device In Cooldown Used | An Airlock 2FA device that is in cooldown was used for authentication or a transaction approval |
| Username concerned by the event |
|
| User's Airlock 2FA account ID |
| ||
| ID of the Airlock 2FA device in cooldown |
| ||
Authentication Flow Successfully Completed | User completed an authentication flow |
| Username concerned by the event |
|
| List of authentication methods used during the authentication flow |
| ||
Context Data Changed | Context data of a user has been changed |
| Username concerned by the event |
|
| Original value of the context data item |
| ||
| New value of the context data item |
| ||
Cronto Device Activated | User activated a new Cronto device |
| Username concerned by the event |
|
| ID of activated Cronto device |
| ||
Cronto Device Deleted | A Cronto device was deleted |
| Username concerned by the event |
|
| ID of deleted Cronto device |
| ||
Device Token Deleted | A device token was deleted |
| Username concerned by the event |
|
| ID of the deleted device token |
| ||
Device Token Registered | A device token was registered |
| ID of the newly registered device token |
|
Email Address Added | An Email address was added to the account |
| Username concerned by the event |
|
| Newly added email address |
| ||
Email Address Changed | The email address of the account was changed |
| Username concerned by the event |
|
| Original value of the email address |
| ||
| New value of the email address |
| ||
Email Address Deleted | The email address of the account was removed |
| Username concerned by the event |
|
| Deleted email address |
| ||
FIDO Credential Deleted | FIDO credential was deleted |
| Username concerned by the event |
|
| Internal identifier of deleted FIDO credential |
| ||
FIDO Credential Registered | User registered a new FIDO security key |
| Username concerned by the event |
|
| Configured identifier of the relying party |
| ||
| Binary data (Base64url encoded) provided by the FIDO authenticator during registration |
| ||
Logged in from new Device | A user logged in from a previously unknown browser or device. |
| Username concerned by the event |
|
| Short name used of the browser. |
| ||
| Short name of the operating system. |
| ||
| Short name of the device. |
| ||
| Code of the country (if geo location available). |
| ||
| Name of the city (if geo location available). |
| ||
MTAN Token Deleted | Mobile phone number was deleted |
| Username concerned by the event |
|
| Identifier of the mobile phone number to be deleted |
| ||
| The phone number to be deleted |
| ||
MTAN Token Phone Number Changed | Mobile phone number was changed |
| Username concerned by the event |
|
| Identifier for the registered mobile phone number |
| ||
| previously registered modile phone number |
| ||
| newly registered mobile phone number |
| ||
MTAN Token Registered | User registered a new mobile phone number |
| Username concerned by the event |
|
| Identifier for the registered mobile phone number |
| ||
| The phone number to be registered |
| ||
Password Changed | User changes his or her password |
| Username concerned by the event |
|
User Created | New user was created |
| Username concerned by the event. |
|
User Deleted | User was deleted |
| Username concerned by the event. |
|
User Locked | User account was locked |
| Username concerned by the event. |
|
| Reason why the user's account was locked. |
| ||
User Roles Changed | There was a change in the roles of the user |
| Name of the user whose roles were changed |
|
| The old roles of the user (before the change) |
| ||
| All the roles of the user after the change |
| ||
| The role(s) added to the user during the change |
| ||
| The role(s) removed from the user during the change |
| ||
User Unlocked | User account was unlocked |
| Username concerned by the event. |
|
Event identification data
Every event provides information to identify a concrete instance uniquely.
Event identification data | ||
---|---|---|
Attribute | Description | Example |
| Identifier which uniquely identifies this event. |
|
| The instant when the event was created. |
|
Event source data
Every event provides information about the source creating this particular instance. Depending on where the event originated from (e.g., Adminapp or Authentication Flow in the Loginapp), different information may be provided that we list below.
Note that every instance of an event has exactly one source.
Event source data | |||
---|---|---|---|
Source | Attribute | Description | Example |
Adminapp |
| Name of the administrator who produced the event |
|
Authentication Flow |
| The configuration context in which this event was produced |
|
| Configured application ID for this authentication flow |
| |
| ID of this authentication flow. For non-custom authentication flows, the value is always |
| |
Non-Authentication Flow (e.g., Protected Self-Service Flow) |
| The configuration context in which this event was produced |
|
| Configured identifier of this flow |
| |
Authentication Flow Step |
| The configuration context in which this event was produced |
|
| Configured application ID for this authentication flow |
| |
| ID of this authentication flow. For non-custom authentication flows, the value is always |
| |
| Identifier for this step if configured |
| |
Non-Authentication Flow Step |
| The configuration context in which this event was produced |
|
| Configured identifier of this flow |
| |
| Identifier for this step if configured |
|
Event metadata
Every event provides information about the request leading to its creation.
Event Metadata | ||
---|---|---|
Attribute | Description | Example |
| Raw value of the User-Agent request header |
|
| IP address of the request |
|