Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Product Opti ID
Created by Guest
Created on May 30, 2024

Allow custom local hostnames for Opti ID CMS integration

Currently, in order to test Opti ID integration with Optimizely CMS in a local development environment, you must use https://localhost:5000 as the host URL. Custom hostnames are not allowed, and you will get an error message back from Opti ID if you try to use a custom URL.

For local development, we often set our sites up in IIS using the hostname format "sitename.local". However, when using Opti ID, we are stuck with using localhost:5000. If we were to have multiple sites using Opti ID, this could cause conflicts, since every site would need to use localhost:5000.

It would be great if we had the ability to whitelist custom local hostnames for use with Opti ID. Or, at the very least, to allow a range of port numbers so that every site does not need to use port 5000. This would be more flexible and less disruptive to our local site setup process. Thanks!