Token-Based Authentication Deprecation in NetSuite 2026.2
NetSuite 2026.2 announces the deprecation of Token-Based Authentication for new integrations, urging migration to OAuth 2.0.
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.
Frequently Asked Questions (4)
Will existing Token-Based Authentication integrations stop working after NetSuite 2026.2?
What do I need to do to prepare for the end of support for Token-Based Authentication in 2028?
How does the token-based authentication deprecation affect user access and permissions?
What will happen if I try to create a new integration using Token-Based Authentication after NetSuite 2026.2?
Was this article helpful?
More in Authentication
- Single Sign-On Only Role Configuration in NetSuite
Configure Single Sign-On Only roles in NetSuite to ensure users can access accounts solely through OIDC SSO.
- Credentials File Management in NetSuite 2026.1
Manage credentials file errors in NetSuite 2026.1, ensuring proper permissions and passkey handling for smooth authentication.
- NetSuite Password Expiration Settings and PCI Rules
Set Password Expiration in Days, prompt employee password changes at next login, and apply PCI rules for unencrypted-data access.
- NetSuite Minimum Password Length and PCI Rules
Set NetSuite password length within policy limits, understand Customer Center treatment, and apply PCI rules for sensitive permissions.
Also from NetSuite 2026.2
- SuiteCloud CLI License Acceptance for Automation
Set SUITECLOUD_CLI_ACCEPT_LICENSE=true to suppress the SuiteCloud CLI license prompt during scripted npm installation.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
- Bank Matching and Reconciliation Enhancements in NetSuite 2026.2
Bank matching and reconciliation pages in NetSuite 2026.2 receive critical UI enhancements for improved transaction management.
- NetSuite AI Connector Service: New Prompt Categories in 2026.2
NetSuite 2026.2 introduces new prompt categories in the AI Connector Service, enhancing user guidance for various business functions.
Advertising
Reach Authentication Professionals
Put your product in front of NetSuite experts who work with Authentication every day.
Sponsor This Category