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.
When we (as an Optimizely DXP customer) expose APIs for partner vendors to invoke, including the Optimizely DXP, we need to ensure that we meet The Group’s security standards and one of the many facets to this is IP whitelisting.
This means we don’t allow just any IP address to invoke our API. We have a firewall that implements a check on the incoming IP address(es) and only allow ones that we know of.
It is a problem if the Optimizely DXP cannot provide us with persistent IP address ranges that we can whitelist on our side. We don’t want our firewall rejecting traffic that are valid form submissions as this would mean losing leads and has material business impact. At the same time we also need to ensure that we do not compromise on security by not implementing any whitelist or implementing a whitelist that is too wide.