Setting SuiteSignOn Basic Definitions
On the SuiteSignOn record for an external application, you (the application provider) must define the following:
-
Name - A name for the application, to appear in NetSuite lists.
-
ID - A script ID for this integration, to be passed as a parameter in the portlet script. The value is automatically prepended with customsso. You should assign a unique script ID to your SuiteSignOn object if you intend to bundle and distribute your integration.
-
Shared Secret - A password used to establish ownership of the Consumer Key generated by NetSuite. This value is included in the signature passed in your HTTP header, and needs to be referenced in your application verification code.
Important:See Notes about Modifying the Shared Secret for tips about changes to this password.
You do not need to define the following:
-
Consumer Key - It is generated by NetSuite. You must include this value in your HTTP header and application verification code.
-
Partner Account - Each customer's account ID for your application. Each customer may need to enter this value after installation of the SuiteSignOn bundle. This value is not necessary if your integrated application does not require this value for identification. Be sure to include instructions for this task in your bundle documentation, if necessary.
-
Web Services Access - Level of access supported for SOAP web services callbacks from integrated applications. The following options are available:
-
Same as UI Role - the default, which allows SOAP web services callbacks from integrated applications with the same level of permissions as in the user interface integration.
-
No Access - prevents integrated applications from accessing NetSuite through SOAP web services callbacks.
-
Additional options for any roles designated as Web Services Only in the account. Selecting one of these roles allows SOAP web services callbacks from integrated applications, but limits access to the permissions levels assigned to the selected role.
As a security best practice, you should provide the minimum level of access required for SuiteSignOn integrated applications. For example, if an application only requires user interface integration, it is best to set the Web Services Access option to No Access.
You can view and edit the Web Services Access field on the SuiteSignOn list page at Setup > Integration > SuiteSignOn.
-
After setting up basic definitions for the SuiteSignOn integration, you can define the connection point to the NetSuite UI. You can also define user identification fields used as context for the integration.
For examples of HTTP header and application verification code, see SuiteSignOn Definitions, Parameters, and Code Samples.