Okta Workflows API Endpoint Alias and Client Token Values Are Not Generated

When an administrator adds the API Endpoint event card to an Okta Workflow and selects the option to secure it with a client token, the Alias and Client Token fields remain blank. This occurs because Okta generates these values only after a workflow save. Saving the workflow after adding the event card resolves the issue and populates the credentials.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Workflows
• API Endpoint event card

Okta populates the Alias and Client Token fields only after adding the API Endpoint event card and saving the workflow. If a workflow save occurs prior to adding the API Endpoint event card, Okta requires another save after adding the card to generate the Alias and Client Token values.

How does Okta generate the Alias and Client Token values?

Create a new workflow, add the API Endpoint event card, configure the security settings, and save the workflow to generate the token values.

1. Create a new workflow.
2. Add an API Endpoint event card.
3. Select the Secure with client token option in the API Endpoint Settings screen.
4. Select Close.
5. Save the workflow.
6. Select the three dots icon at the bottom of the API Endpoint card and choose Endpoint Settings. Okta populates the Alias and Client Token fields with values.