10.7.2 NetSuite - Configuring Report Authority to work with NetSuite

Once you have configured NetSuite to work with Report Authority (as detailed in the previous article), you will need to configure the Report Authority client to work with the integration created.

Enabling Report Authority to Receive NetSuite Authentication Tokens from the Browser

Report Authority needs to be given rights to receive the NetSuite Authentication Tokens from the Browser. This will need to be done on each end-users' computer by someone with admin rights.

To grant the necessary permission, click Start and type Command Prompt. In the Command Prompt, copy and paste the following command and press enter:

netsh http add urlacl url=http://localhost:80/netsuite/ user=everyone.

Create User Bindings

This process will create a "binding" to a particular NetSuite application. A separate binging will need to be created for every environment that you wish Report Authority to connect to - such as Dev, Test and Production

To create a binding:

Launch Report Authority.
Load an existing document, or create a new blank document.
Click Data -> Manage Connections.
Click the NetSuite tab.

Click Add.
Name the connection.
Click the dropdown combobox for Binding and click the "Create Binding..." button.

Give the binding a name (eg. Dev, Test or Prod)
Enter your NetSuite account ID. This is the 7-digit number in the URL that is displayed when you have logged into the relevant application:

Enter the Role ID for the Report Authority role that was created when the NetSuite bundle was installed. It can be found in NetSuite by clicking Setup -> Users/Roles/ -> Manage Roles. Click on the user role "Report Authority" and retrieve the ID from the URL:

Enter the Consumer Key and Consumer Secret that was displayed when you created the NetSuite integration described in the previous article.
Enter the same Callback URL that was used when the integration was created (the default suggestion is "http://localhost/netsuite").
Click OK.

This process must be repeated for each environment.

Deploying User Bindings as Application Bindings

The above process outlines how user bindings are created. The disadvantage of using user bindings when deploying Report Authority is that;

The process would need to be followed by all users of the software.
Documents shared between users of the application would only work if the bindings were all given the same name.
From a security perspective - it may not be desirable to share the Consumer Keys and the Consumer Secrets to all employees.

To overcome these shortcomings, you can instead deploy the NetSuite bindings XML file along with the software so that all users automatically have the same bindings pre-loaded into their instance of Report Authority.

To deploy an Application binding:

Create a user binding as described above for a single user.
Copy the resultant bindings XML file. This file contains all the parameters including encrypted versions of the Consumer Keys and Consumer Secrets. The file is called "OneStream.Bindings.xml" and can be found in the folder "C:\Users\{username}\AppData\Roaming\Authority_Software\Report Authority Professional\Adapters\"
This file should be copied, and placed into each user's application folder "C:\Program Files (x86)\Authority Suite\Report Authority Professional v{nn.n}\Configuration". This can be done manually by someone with admin rights on the computer or automatically as part of a software deployment process.