Security Breached Credential Detected
Trigger a flow when Okta receives a report that user credentials have appeared in a list of breached credentials.
This event card isn't available for flows in Okta for US Military or Okta for Government Moderate.
Scopes
See Event cards for the list of required OAuth scopes needed by this card.
Output
| Field | Definition | Type |
|---|---|---|
|
Output |
||
|
Date and Time |
The date and time the event was triggered in the Okta API. |
Text |
|
Message |
Message details about the event. |
Text |
|
Event ID |
Unique identifier of the event. |
Text |
|
Event Type |
Type of event that was published. |
Text |
|
Event Time |
Time stamp when the notification was delivered to the service. |
Text |
|
Version |
Versioning indicator. |
Text |
|
Okta User |
Details about the Okta user whose credentials have appeared in a list of breached credentials. |
Object |
|
ID |
ID of the Okta user account. |
Text |
|
Alternate ID |
Email address of the Okta user. |
Text |
|
Display Name |
Display the name of the Okta user. |
Text |
|
Type |
Type of Okta user. |
Text |
|
Credentials |
The list of breached credentials. |
List of Objects |
|
ID |
ID of the breached credential. |
Text |
|
Alternate ID |
Alternate ID of the breached credential. |
Text |
|
Display Name |
Display the name of the breached credential. |
Text |
|
Type |
Type of the breached credential. |
Text |
|
UUID |
Webhook event's universal unique identifier. |
Text |
|
Event Details |
Raw JSON payload returned from the Okta API for this particular event. |
Object |
|
Headers |
The object representing the headers for the response. Each key of the header is parsed into a header string as "key: value". For example, Content-Type: text/plain. |
Object |
|
Source |
An API link to the associated Okta Event Hook. |
Text |
|
Debug Context |
Object |
|
|
Debug Data |
Information on the triggered event is used for debugging. For example, returned data can include a URI, an SMS provider, or a transaction ID. |
Object |