User MFA Factor Activated
Trigger a flow when a user activates a new multifactor authentication (MFA) factor.
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.
Output
| Field | Definition | Type |
|---|---|---|
|
Date & 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 | Okta admin who enrolled the user in MFA. |
Object |
| ID | ID of the Okta admin who enrolled the user in MFA. |
Text |
| Alternate ID | Email address of the Okta admin. |
Text |
| Display Name | Display name of the Okta admin. |
Text |
| Type | Type of Okta admin who enrolled the user in MFA. |
Text |
| Okta User | Okta user who activated a new MFA factor. |
Object |
| ID | ID of the Okta user. |
Text |
| Alternate ID | Email address of the Okta user. |
Text |
| Display Name | Display name of the Okta user. |
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.
Trigger a flow with the User MFA Factor Activated event card
To trigger a flow, you must use a mobile device and complete these steps:
-
Using a test account, in the Admin Console, go to .
-
Verify that at least one factor is active. Factors that are already activated are designated as such with green check marks.
-
To activate a factor, select one from the Factor Type list and select Activate from the drop-down for that factor.
It is recommended that you activate the Okta Verify, SMS Authentication, or Security Question factors.
-
In the top right corner of the Admin Console, click the account dropdown menu, and then click My settings.
-
In the Extra Verification section, click Set up for the new factor that you selected previously, then complete the steps to activate that factor.
When you have completed the activation of the new factor, any flow using the User MFA Factor Activated event card will be triggered.