Okta Workflows Preview release notes

Generally Available features

Client token no longer appears in Invoke and Resume URLs

When you secure a flow with a client token, the token no longer appears in the Invoke URL or Resume URL. This keeps the token out of places where URLs get logged, cached, or shared. Send the client token in the x-api-client-token header instead. Existing callers that pass the token as a clientToken query parameter continue to work.

Harmony SASE connector renamed to Check Point SASE

The Harmony SASE connector is now named Check Point SASE to match the updated product name. The connector's description and icon have also been updated. Your existing flows and connections aren't affected.

Fixes

• The API Connector didn't appear in the Connected Apps section of the action catalog, even when the user had a connection for it. (OKTA-1240035)

• In Integration Builder, deleting a project that contained only a test connection returned an HTTP 500 error with no explanation. (OKTA-1271603)

• Turning off a flow that used a webhook event card failed on the first attempt with the message "Cannot deactivate Flow. Webhook de-registration failed." This happened with connectors whose webhook removal request returns no content, such as the Kaonavi connector. The flow turned off on the second attempt. (OKTA-1302836)

• When users changed the input of a card, that was inside an If Error card, to come from a different card that returned the same data type, the change wasn't shown in the flow's change comparison. (OKTA-1314747)