What to Do to Prepare for the End of Support

Following options can help you identify integrations in your account that might be affected by the TBA end of support.

Build and Integration Inventory (Ideal First Step)

Create a list of every integration that connects to NetSuite, including:

Integration Name
Owner of the integration - whether the integration is internal, or it was created by a third-party vendor.
NetSuite service/channel used - whether you used SOAP or REST web services, RESTlets, or SuiteAnalytics Connect
Authentication method used - whether the integration uses TBA, OAuth 2.0, user credentials, or any combination of those.
Confirmation of OAuth 2.0 support - this applies to the third-party apps. You should ask the integration author whether the application can support OAuth 2.0.

This list becomes your migration tracking document and helps you identify high-risk dependencies.

For more information about integration records, see Creating an Integration Record.

Search Your Login Audit Trail

You can create a saved search for your Login Audit Trail.

Set up the following criteria in the saved search:

Toke-based Access Token Name, with the value is not empty.
Date, with a value is after with a time range up to 12 months. The time range helps you determine whether the integration has been used recently.

On the Results tab, add a row for the Token-based Application Name with a Summary Type: Group.

For more information about a saved search, see Saved Searches

Set up a Specific Integration Record Test Window

There are two options to test the TBA end of support on a specific integration record. However, both these options only work with integration records that you own. If the integration was installed from a different account (for example, a third-party application), you will not be able to test it.

On the integration record that you want to test

Ensure that all boxes in the Token-based Authentication section are cleared.
Make a note of the Callback URL, so you can safely turn TBA on, when you're done with the testing.
Click Save.

The integration stops working. You can return it to the previous state by checking the boxes in the Token-based Authentication section and pasting the original value in the Callback URL field.

Alternatively, you can change the value of the State field on the integration record to Blocked. This has a similar effect as the first option, but you don't have to store the Callback URL, because it isn't deleted from the record. You can change the value of the State field to Enabled when you finish testing. This option turns off the whole integration record, not only the TBA setup.

Account-wide Test Window

You can disable the Token-based Authentication feature in your account to test the impact of the end of support. Keep in mind that disabling the feature also affects SuiteAnalytics Connect, if you're using it with TBA.

To disable the Token-based Authentication feature:

Go to Setup > Company > Enable Features.
On the SuiteCloud tab, scroll down to the Manage Authentication section.
Clear the Token-based Authentication box.
Click Save.

You can reenable the Token-based Authentication feature after you finish testing.