When onboarding Optimizely Content Management System (CMS) instances with Opti ID, you may add your own custom domains to individual instances so you can access these instances through their own domains and sub-domains. This process can take up to 24 hours to take effect. If your CMS solution representative adds domains and they are not working, wait up to 24 hours until contacting Optimizely Support.
This article describes three scenarios that indicate the domains have not fully propagated to Optimizely's systems.
400 error or no Opti ID global navigation
If you receive a 400 error when you log into Opti ID (https://login.optimizely.com) or you do not see the Opti ID global navigation bar when you log into your CMS instance, you likely have not enabled Opti ID for your CMS instance.
You must enable Opti ID for your CMS instance and install the NuGet package before your users can log in to Opti ID.
Contact Optimizely Support if you are not already scheduled to migrate to Opti ID.
CORS errors
If you open your browser's developer tools and see CORS errors from https://usermgmt-api.optimizely.com, there is an issue with this process. If it has been more than 24 hours since your Optimizely representative confirmed they added domains, contact Optimizely Support.
Bad requests from Okta
If you receive a 400 Bad Request error when trying to log in, it may indicate a configuration issue. If it has been more than 24 hours since your Optimizely representative confirmed they added domains, contact Optimizely Support.
Article is closed for comments.