Part 1: User-based vs Token-based Authentication (Netsuite to Planning Cloud Integration)

     I can't believe it's been another year since my last update, it seems that time really does go fast when you're having fun.

Well now that the fun is over and travelling and socialising have ground to a halt, I at least have the opportunity to give back some of the things I've learnt over the year. 

This blog series will focus on what I learnt when integrating Netsuite with Planning Cloud (PBCS) using the in-built adapter. 

**Part 1 - User based vs Token Based Authentication**    

      Part 2 - Tips on setting up your Saved Search in Netsuite

      Part 3 - Tips on setting up Data Management in Planning Cloud 

      Part 4 - How to set up Drill through from Planning Cloud to Netsuite

      Part 5 - How to give your end users access to run the integrations 

I do not like to repeat anything that has been well documented before, so in this blog I will not be going through the steps needed to install and configure the PBCS bundle in Netsuite. My colleague Mike has done this in an entertaining and thorough way in the following blogs:

https://stay-ahead-in-the-cloud.blogspot.com/2019/03/connecting-two-clouds-netsuite-to.html

https://stay-ahead-in-the-cloud.blogspot.com/2019/07/setting-up-custom-role-for-netsuite-integration.html

I am by no means a Netsuite expert, the lessons learnt I am going to share with you are a direct result of my (often trial and error) experience and there may be better ways to achieve the same thing (although I have not found them!)   

      Please note: This blog series assumes you already have a basic understanding of how Netsuite works, you have installed the PBCS bundle in Netsuite and that you have set up your PBCS Integration user and role.  

     So without any further ado, welcome to Part 1. 

     User-based vs Token-based Authentication

     When using Netsuite as a Source of data for Planning cloud, there are two options for creating a connection between the systems; user-based authentication and token-based authentication. Let’s briefly look at the differences:

     User-based authentication

     Whilst user-based authentication is simpler to set up, it requires storing credentials for the integration and results in a password that expires every 180 days. This can be problematic if the administrator forgets to update the password before it expires as it will result in the integration failing. This is obviously bound to happen at the most important time during the month-end cycle, resulting in unnecessary disruption to the business.  

     Token-based authentication

     This method is more secure and best practise. It involves using consumer and token ID/secret pairs to authenticate the connection. There will be no expiring password so no need to worry about avoidable disruption. One less reminder in the diary 😊

     As usual, I find the standard documentation quite confusing when it comes to setting up token-based authentication, but like anything, it is easy when you know how. 

     How to set up token-based authentication: 

     Enable token-based authentication

     Before being able to use token-based authentication in Netsuite, you will need to enable it by going to Setup > Company > Enable Features

     

     Go to the SuiteCloud tab, scroll down to Manage Authentication and check the box for Token-Based Authentication

      

     Once your PBCS Integration User and Role are set up (see Mike’s blogs above), you can generate your Consumer ID/Secret and Token ID/Secret. 

     Generating the Consumer ID/Secret

     1. Go to Setup > Integration > Manage Integrations

     

     2. Name the Integration e.g. PBCS Integration TBA  

     Check the boxes for Token-Based Authentication, TBA: Issuetoken endpoint

     Uncheck all boxes in the OAuth2.0 section

     Optionally check the box for User Credentials if you also wish to be able to use that method.

     When you click Save, you will be shown the Consumer ID/Secret – this is only shown once so make a copy of it and keep it safe. If you lose it you will have to repeat this step to create a new Integration. 

     

      Generating the Token ID/Secret

    1.      Now go to Setup > Users/Roles> Access Tokens

        

     2. Create a new Access Token, selecting your newly created Integration, your integration user and integration role. Once you save this, you will be shown the token ID/secret. Again, take a copy and keep this safe as it is only shown once.

           

     

      And Voila, that’s all you need! Now you just need to enter these into the source system configuration in Data Management.

      Note: Your Netsuite account number can be found in your Netsuite URL.

       

Any questions, feel free to drop me a comment.

That concludes Part 1, stay tuned for Tips on setting up your saved search in Netsuite.

Thanks for reading :) 

Ciao for now.