Okta Workflows Console Requires Authentication Against a Custom Domain
Last Updated:
Overview
When an organization contains a single custom domain, administrators must authenticate against that custom domain when accessing Okta Workflows. This expected behavior occurs because Okta Workflows is custom domain aware and defaults to the custom domain when only one is present. Administrators may experience an unexpected authentication prompt when attempting to access the Okta Workflows console.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Workflows
- Custom Domain
Cause
Okta Workflows is custom domain aware. When exactly one custom domain exists in the Okta organization, Okta Workflows automatically defaults to that domain, triggering an additional authentication prompt for administrators accessing the console.
Solution
Why does the authentication prompt occur with a single custom domain?
This is expected behavior. Okta Workflows requires authentication against the custom domain when only one custom domain exists in the Okta organization. Future events regarding Okta Workflows licensing may also trigger an authentication switch from the default Okta domain to the custom domain.
Okta Workflows Behaves Differently When Multiple Custom Domains Exist
The authentication prompt to a custom domain does not appear when the Okta organization contains more than one custom domain. In this scenario, Okta Workflows Console access cannot determine which custom domain to use and defaults to the standard Okta domain for authentication.
