The SuiteSignOn (The NetSuite proprietary Outbound Single Sign-on feature) uses two parameters for mapping during the outbound HTTP call: the dc and env parameters. As of March 1, 2021, these parameters will be deprecated. You must start using the systemDomain and webservicesDomain parameters instead.
What is Changing?
As of March 1, 2021, the dc and env parameters in the Outbound SSO HTTP call will be deprecated. You should not use the dc and env parameters. To construct a URL for the ssoapplistener.nl endpoint, use the domain from the new parameter systemDomain.
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. The webservicesDomain parameter is used if your integration uses optional SuiteTalk web services calls. For more information, see SuiteSignOn Sequence Diagram and Connection Details (SuiteAnswers, ID 10714).
See below the example of the new Outbound SSO HTTP call:
/SSO/demoApp.php?context=user_123456_PROD&oauth_token=030f6c1d1b6b106c6b445655477e72529fdea42ef310ab10&dc=001&env=PRODUCTION&systemDomain=https%3A%2F%<accountID>.app.netsuite.com&webservicesDomain=https%3A%2F%<accountID>.suitetalk.api.netsuite.com
Please note that the dc and env parameters are still present in the HTTP call, but you should not use them. Using the hard-coded mapping between the dcparameter and the URL might cause problems when your account is moved to a different data center that is missing in your mapping.
Required Action:
Before March 1, 2021, ensure that you do not use the dc and env parameters for mapping during the Outbound single sign-on request. Update your 3rd party application to use the systemDomain and webservicesDomain parameters.
If you require assistance or more information, please contact NetSuite Customer Support.