Token-Based Authentication Deprecation in NetSuite 2026.2

TL;DR: Starting in NetSuite 2026.2, new integrations using Token-Based Authentication (TBA) will no longer be supported. Users are encouraged to transition to OAuth 2.0 to ensure their applications remain functional and secure.

What Changes Are Being Implemented?

As of NetSuite 2026.2, the ability to create new integrations that use TBA for authentication will be discontinued. This includes the IssueToken endpoint and the three-step TBA authorization flow. This transition is a preparatory measure for the complete end of support for TBA, which is anticipated in the 2028.1 release. Existing integrations relying on TBA will maintain their functionality until the final end of support.

Why Is This Important?

The phasing out of TBA emphasizes NetSuite's shift towards OAuth 2.0, which promises greater security and more robust features. Users are urged to migrate to OAuth 2.0 at their earliest convenience to avoid disruptions in service. For a comprehensive guide on integrating OAuth 2.0, please refer to the relevant NetSuite documentation.

Who This Affects

• Developers: Need to update integration methods to align with the new authentication protocols.
• Administrators: Should prepare for support changes and facilitate transitions in user access and permissions.
• Security Teams: Must ensure that applications maintain security compliance during and after the transition.

Key Takeaways

• New TBA integrations will not be supported as of NetSuite 2026.2.
• Existing TBA integrations will remain functional until the complete deprecation in 2028.1.
• Users should transition to OAuth 2.0 for improved security and functionality.
• Planning for this shift now can prevent future integration issues.
• Refer to OAuth 2.0 documentation for detailed integration guidance.