Troubleshoot Cloudsuite Distribution in v1 sandbox environments
Due to Infor’s changeover of SSL cipher suites for CSD environments, Optimizely has discovered that v1 (Pod) sandbox environments do not have the correct cipher suite to support this connection. This is a temporary issue as the near-term goal is to move all customers to containers. V1 Production is also unaffected.
To determine if a customer is in a v1 environment, look at the URL for their sandbox.
- Not affected: Environments of {CLIENT}.commerce.insitesandbox.com
- May be affected: Environments of {CLIENT}.insitesandbox.com (without .commerce)
In the meantime, Optimizely has tested and confirmed a reverse proxy solution to correctly route these requests through supported ciphers.
To implement this reverse proxy solution, you must change the target domain in your connections.
- For endpoints that target the API endpoint like https://mingle-ionapi.inforcloudsuite.com/{CLIENT}/SX/rest/sxapirestservice/ , replace the inforcloudsuite.com domain with proxy-api.insitesofthosting.com. For example, https://proxy-api.insitesofthosting.com/{CLIENT}/SX/rest/sxapirestservice/
For endpoints that target the SSO endpoint (for bearer tokens) like https://mingle-sso.inforcloudsuite.com:443/{CLIENT}/as/token.oauth2, use proxy-sso.insitesofthosting.com. For example, https://proxy-sso.insitesofthosting.com/{CLIENT}/as/token.oauth2.
If you have any questions or concerns implementing this solution, please contact your Customer Success Manager.