User MFA Factor Suspended
Trigger a flow when a user suspends an MFA factor in Okta.
This event card is being deprecated from the Okta connector. Replace this event card with the identical card found in the Okta Devices connector. There's no change in the card name or functionality.
Scopes
See Event cards for the list of required OAuth scopes needed by this card.
Output
| Field | Definition | Type |
|---|---|---|
| Date and Time | Date and time that 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 |
|
Admin |
||
| ID | Unique identifier of the Okta admin suspending the user MFA factor. |
Text |
| Alternate ID | Email address of the Okta admin. |
Text |
| Display Name | Display name of the Okta actpr. |
Text |
| Type | Role of the Okta admin. |
Text |
|
Okta User |
||
| ID | Unique identifier of the Okta user whose MFA factor was suspended. |
Text |
| Alternate ID | Email address of the Okta user. |
Text |
| Display Name | Display name of the Okta user. |
Text |
| Type | Type of Okta user. |
Text |
| Reason | Outcome of the MFA factor being suspended. |
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 | Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (Content-Type: text/plain). |
Object |
| Source | Source of user-specific data. |
Object |
|
Debug Context |
||
| Debug Data | Information on the triggered event used for debugging; for example, returned data can include a URI, an SMS provider, or transaction ID. |
Object |
While you can create more user or group fields for an Okta event, the Okta API only returns values for four fields: ID, Alternate ID, Display Name, and Type.
No other fields are supported for users or groups, and this event card doesn't return data from such fields.