This article explains the transitioning process from deprecated events in the Okta connector to the same events implemented in the Okta Devices connector.

Okta announced this upcoming change back in September: Okta Device Events Moved from the Okta Connector to the Okta Device Connector

The following list of Okta event cards will stop working December 11, 2024 in Preview and December 17, 2024 in Production.

• Authenticator Activated

• Authenticator Deactivated

• Device Activated

• Device Added to User

• Device Deactivated

• Device Deleted

• Device Enrolled

• Device Suspended

• Device Unsuspended

• Phone Verification Call Sent

• Phone Verification SMS Sent

• User MFA Factor Activated

• User MFA Factor Deactivated

• User MFA Factor Reset All

• User MFA Factor Suspended

• User MFA Factor Unsuspended

• User MFA

• Device Removed From User
  
  

If the above event cards are not deleted from a flow before they are fully removed from the Okta connector, the Webhook events created by these event cards will remain in the Okta API.

To be able to utilize these Okta events in the future, users must replace them with the event cards with the same name and functionality located in the Okta Devices connector.

All Okta events related to devices have moved from the Okta Connector to the Okta Devices Connector as of 2024.05.1. Existing flows are not affected at this time, but customers need to replace their Okta events with Okta Devices events. The cards will be identical, so is possible to drag the same fields into the flows. 

All of the events must be replaced on the affected list by December 11, 2024 in Preview and December 17 in Production, or their flows will stop working.

Frequently Asked Questions

How to replace the deprecated event card before it is deleted from the Okta connector?

Perform the following steps:

1. Turn off the flow with the deprecated event card.

2. Remove the deprecated event card from the flow.

3. Add a new event card with the same name from the Okta Devices connector.

4. Create a new connection to the same Okta instance as in the deprecated card if needed.

5. Replace the output values from the deprecated card with the output fields of the new card in other cards of the flow.

6. Turn on the flow.

Do I need to replace other Okta connector cards together with the deprecated event card?

No. Other Okta event and action cards remain the same and will proceed to work in the same way.

What if I do nothing and keep the deprecated event cards in my flows?

The flows remain active but they will not be triggered in case the event happens in the Okta platform.

What if I missed the release date when the deprecated event was fully removed from the Okta connector?

You need to perform the following steps to successfully deactivate the flow where the deprecated event is used and delete the Webhook event in the Okta API:

1. Turn off the flow with the deprecated event card.

2. The turn-off process may take some time(up to 1 minute) to execute and might result in an error and the following error toast message appears in the bottom right corner of the flow page.

   

3. In case the flow status did not change from Flow is On to Flow is Off you need to refresh the page and verify that the flow has the Flow is Off status.

4. Note that the registered Webhook event was not deleted from the Okta API.

I did not remove the deprecated event cards in time. How can I delete the registered Webhooks from the Okta API?

Prerequisites:

1. Make sure you have a valid connection to the Okta instance used by the deprecated event card

2. Execute the Okta Custom API Action card to fetch the list of Webhook events with the following payload:

   1. Request Type: GET

   2. Relative URL: /api/v1/eventHooks

   3. Query: { "category": "FLOW" }

3. Expand the Response Body output field to investigate the returned list of event objects

4. Search for the registered Webhook event using the name attribute of each event object. Here are a couple of things to consider while searching for the target event:

   1. An event hook object created by the deprecated Okta event card must have the FLOW_EVENT value for the event.target property of the event object.

   2. The value of the name attribute in the event hook object created by the deprecated Okta event card has the following format: <Okta Event card name> - FLOW-EVENT - <random characters>

      1. Please note that some event hook object names may differ from the actual Okta event card names. Find the relation of the deprecated Okta event card names and their respective event hooks object names below(the difference is underlined):
         Authenticator Activated: Authenticator Activated - FLOW_EVENT - <random characters>
         Authenticator Deactivated: Authenticator Deactivated - FLOW_EVENT - <random characters>
         Device Activated: Device Activated - FLOW_EVENT - <random characters>
         Device Added to User: Device Added to User - FLOW_EVENT - <random characters>
         Device Deactivated: Device Deactivated - FLOW_EVENT - <random characters>
         Device Deleted: Device Deleted - FLOW_EVENT - <random characters>
         Device Enrolled: Device Created - FLOW_EVENT - <random characters>
         Device Suspended: Device Suspended - FLOW_EVENT - <random characters>
         Device Unsuspended: Device Unsuspended - FLOW_EVENT - <random characters>
         Phone Verification Call Sent: Phone Verification Call Sent - FLOW_EVENT - <random characters>
         Phone Verification SMS Sent: Phone Verification SMS Sent - FLOW_EVENT - <random characters>
         User MFA Factor Activated: User MFA Factor Activate - FLOW_EVENT - <random characters>
         User MFA Factor Deactivated: User MFA Factor Deactivate - FLOW_EVENT - <random characters>
         User MFA Factor Reset All: User MFA Factor Reset All - FLOW_EVENT - <random characters>
         User MFA Factor Suspended: User MFA Factor Suspended - FLOW_EVENT - <random characters>
         User MFA Factor Unsuspended: User MFA Factor Unsuspended - FLOW_EVENT - <random characters>
         User MFA: User MFA - FLOW_EVENT - <random characters>
         Device Removed From User: Device Removed from User - FLOW_EVENT - <random characters>

5. Take the value of the id attribute in the found event hook object

To be able to remove a Webhook event created by a deprecated Okta event card perform the following steps:

1. Run the Okta Custom API Action card with the following data and verify the Response Body object contains "status": "INACTIVE":
   Request Type: POST
   Relative URL: /api/v1/eventHooks/<event hook id>/lifecycle/deactivate

2. Run the Okta Custom API Action card with the following data and verify the Response Status Code has the 204 code
   Request Type: DELETE
   Relative URL: /api/v1/eventHooks/<event hook id>

3. The Webhook event was deleted from the Okta API