Netsuite token based account
Hi All,
Recently netsuite updated to token based, Anyone making use of netsuite token based account to access netsuite.
Thanks,
Umashankar
Forum Discussion
Sombit, I’m unclear on what you’re saying here. Can you please give a link to some documentation about what you’re referring to?
I implemented our support for NetSuite’s Token Based Authentication in our NetSuite snap pack a few years ago and as far as I know, nothing has changed about our implementation since 2017 and nothing has changed in terms of the NetSuite requirements either. Our implementation has always used an Application ID, Consumer Key and Consumer Secret that are completely hidden from the end user. These values are associated with the “SnapLogic” integration that everyone must import into their NetSuite account and create their tokens against. It has never worked any differently than that. Please review our documentation about how to import the SnapLogic integration record into your account through NetSuite’s SuiteBundle mechanism, and how to create a token against this record. Visit this page and click on the “Know more about generating the Token ID…” link:
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438997/NetSuite+Account
Also, please share a screenshot of your NetSuite Token Account settings.
Re-reading your post, it strikes me that the issue may be that an older version of the NetSuite snap pack was incorrectly reporting a successful validation for a NetSuite Token Account that wasn’t in fact valid, and the newer version of the pack is correctly reporting that the account is invalid. Were you able to actually use this account with the NetSuite snaps to successfully create/read/update data?
