This notice is intended for customers who use the Outbound Single Sign-on (SuiteSignOn) feature as an authentication method in your account, with the dc and env parameters for mapping. Using the dc and env parameters will cause your integration to fail after your account is moved into a different data center.
What is Changing?
The dc and env parameters in the Outbound SSO HTTP call will be deprecated.
To help you discover potential production account failures that your existing parameter mappings might cause, we have scheduled a test window.
What Will Happen During the Test Window?
The 24-hour test window will enable you to see the effects of removing the dc and env parameters in your account on your integrations. The dc and env parameters will be removed from the outbound HTTP call and the mapping will stop working.
The 24-hour test window will begin on Monday, May 10, 2021 at 12:00 a.m. PDT.
After the test window ends, the dc and env parameters will return to the outbound HTTP call.
Required Action:
After the test window ends, update your 3rd party application to use the systemDomain and webservicesDomain parameters. To construct a URL for the ssoapplistener.nl endpoint, use the domain from the new parameter systemDomain. Ensure that you do not use the dc and env parameters for mapping during the Outbound single sign-on request. Follow these guidelines:
- The value for the systemDomain parameter is the account specific domain.
- The value for the webservicesDomain parameter is the account specific SuiteTalk web services domain.
- You need to use the webservicesDomain parameter only if your integration uses optional SuiteTalk web services calls.