SuiteScript in an OAuth first world
Two authentication changes are landing on the same release. Here is what that means for anyone maintaining custom SuiteScript integrations.
What actually changes
Between the SOAP retirement and the coming end of token based authentication for new integrations, the authentication layer under most custom SuiteScript work is shifting under its feet.
A practical audit checklist
- List every integration and custom script touching NetSuite, including ones nobody currently owns.
- Mark the authentication method for each one: SOAP, TBA, or OAuth 2.0.
- Note the last time each integration's API or WSDL version was touched.
- Prioritize by business criticality, not by ease of fixing.
- Assign a named owner and a target migration quarter to each item on the list.
If your team has already run this audit, or is in the middle of one, that is a good topic for a chapter session. This is a group problem more than an individual one, and the fastest way through it is comparing notes with people who have already done the work.