1. Account Administration
  2. Authentication
  3. Authentication Overview
  4. Preparing for Token-based Authentication (TBA) End of Support

Preparing for Token-based Authentication (TBA) End of Support

NetSuite plans to end the support for the Token-Based Authentication (TBA) feature. This change will affect integrations that authenticate using the TBA credential set (for example, consumer key/secret plus token ID/secret).

Starting in NetSuite 2027.1, you will no longer be able to create new integrations that use TBA for SOAP and REST web services, and RESTlets.

Later, (tentatively NetSuite 2028.1) the support will end for existing integrations, excluding the SuiteAnalytics Connect (ODBC/JDBC).

To avoid service disruptions, you should identify where you use TBA and update the affected integrations to use the OAuth 2.0 feature.

What Will Stop Working After the End of Support

  • Custom RESTlets

    Custom scripts or applications that call RESTlets using TBA will no longer authenticate successfully

  • SOAP web services integrations

    When the support ends for SOAP web services, the integrations will no longer authenticate successfully.

  • REST web services integrations

    REST web services integrations that use TBA will fail authentication, and no new use cases be configured.

  • Third-party connectors and apps

    Third-party and app connectors that still rely on TBA may require an updated configuration, or a connector version update to support OAuth 2.0. These include, for example, Boomi, Celigo, MuleSoft, or Informatica.

  • Any external application, custom script, or integration using TBA credentials to authentication in NetSuite.

    Any application you use in NetSuite that authenticates with TBA credentials (consumer ID and consumer secret) will stop working when the TBA support ends.

Related Topics

General Notices