When a custom URL domain is introduced to their Okta organization, Okta administrators should update the application configuration. This article discusses how this action impacts end-users and provides Okta's recommended guidelines for altering URLs.
- Okta administrators
- Custom domains
- Applications configured in Okta
- End-users
The session cookie produced for an Okta tenant is linked to the accessed URL. Consequently, if an end-user accesses the Okta tenant from a custom URL and then tries to use an application configured with the standard subdomain.okta.com URL, they will be prompted to re-authenticate to align the session cookie with the application's URL and vice versa. This situation can be inconvenient for end-users if different applications are configured with differing URLs, requiring continuous re-authentication.
Administrators are advised to update all applications with the custom URL to circumvent re-authentication problems for end-users. Ideally, this update should be performed during a scheduled maintenance window over a weekend to minimize disruption to end-users.
Administrators should aim to use a single custom URL for all applications to minimize impact and confusion for end-users. This strategy ensures a consistent user experience and eliminates the requirement for frequent re-authentication.
