Eliminating Password Expiration Issues and Maintenance in the Salesforce-NetSuite Integration App

For the Salesforce-NetSuite Integration App, to eliminate password expiration issues and maintenance we highly recommend a non-expiring Salesforce password login coupled with using Token Based Authentication (TBA) in NetSuite. For more information on TBA, see these documents: Token-based Authentication: What and Why,  Token-based Authentication: Instructions

If you must use an expiring password login in NetSuite, we recommend that your system administrator tag his/her calendar to proactively change the NetSuite password before expiration and update the Integration App and integrator.io accordingly. See this document for details.

The remainder of this article covers setting up that Salesforce login.

Your Salesforce organization may have stringent password expiration policies for all users, but when integrating with Salesforce, a username and password is required for API use. Unless the profile selected for the Integration App is set to never expire, integration administrators are required to update the password in integrator.io after changing the user's password periodically.

To mitigate this step, and ensure no interruption of services, the Salesforce profile used by the Integration App can be set to never expire.

 Only custom profiles can be set for passwords to never expire. So a profile would need to be cloned, updated to never expire, and applied to the user associated with the Integration App. To set this up, follow the instructions below.

1. Clone an existing standard profile: Go to Setup > Administer > Manage Users > Profiles 
2. Select Clone for an existing standard profile.
3. Name the new profile.