User MFA Factor Deactivated
Trigger a flow when a user deactivates a multifactor authentication (MFA) factor.
Output
| Field | Definition | Type |
|---|---|---|
| Date and Time | Date and time that the event was triggered in the Okta API. | String |
| Message | Message details about the event. | String |
| Event ID | Unique identifier of the event. | String |
| Event Type | Type of event that was published. | String |
| Event Time | Timestamp when the notification was delivered to the service. | String |
| Version |
Versioning indicator. |
String |
| Admin | Okta admin who enrolled the user in MFA. | Object |
| ID | ID of the Okta admin who enrolled the user in MFA. | String |
| Alternate ID | Email address of the Okta admin. | String |
| Display Name | Display name of the Okta admin. | String |
| Type | Type of Okta admin who enrolled the user in MFA. | String |
| Okta User | Okta user who deactivated an MFA factor. | Object |
| ID | ID of the Okta user. | String |
| Alternate ID | Email address of the Okta user. | String |
| Display Name | Display name of the Okta user. | String |
| UUID | Webhook event's universal unique identifier. | String |
| 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 additional user or group fields for an Okta event, the Okta API only supports four fields for Okta connector event cards: ID, Alternate ID, Display Name, and Type. Values will be returned for these four input fields only. No other fields are supported for users or groups, and data from such fields will not be returned by this event card.
Trigger a flow with the User MFA Factor Deactivated event card
To trigger a flow, you must already have a factor activated. Complete these steps:
-
Using a test account, in the top right corner of the Admin Console, click the account drop-down then click My settings.
-
In the Extra Verification section, click Remove for the factor that you want to deactivate.
-
Click Yes to confirm the removal of the factor.
When factor is removed, any flow using the User MFA Factor Deactivated event card will be triggered.