I am attempting to deploy to SCA using the new Token Based Authentication method, and need to create a token. However, when the web browser window pops up it shows an error message: An unexpected error has occurred. Please go back and try again. This is SCA Vinson, with the Token Based Authentication patch/changes applied. I am logged into Netsuite and have tried with both Administrator and SCA Deployer roles active. Does it matter what you enter for authID? That isn't clear to me.

Open Commons\ns_npm_repository\oauth1\index.js and change

const hostnameStep1 = this.vm ? hostName : `rest${molecule}.<http://netsuite.com|netsuite.com>`;

to

const hostnameStep1 = this.vm ? hostName : `system${molecule}.<http://netsuite.com|netsuite.com>`;

I have made that change, but still get the same result.

@bbeach You can add a new token in your .nstba file. It works

@Swathi I do not have this file, I can create it and add the token manually, but I need to know the correct formatting.

{ “xxx”:{ “token” : “ ” “secret” : “ “ “account” : “account ID” } } xxx is the token Please generate token and secret in your NS account

@Swathi thanks, I was able to generate the token in NS, and create the file. The deploy process recognizes the token, but after selecting it it seems to hang and do nothing from there.

You might need to double check your patch applied and also check if everything is setup correctly for the 2FA, such us enable features, SCDeployer with the right permissions, add the SCDeployer to the deployment reslet used for your version, etc. Check the docs these things are listed in an article.

2FA is active and working on the account, but I will review all permissions and settings again. I am also double checking my patch, but so far everything appears correct. I have opened a support case for this.

Hi @bbeach I seem to be having the same issue, were you able to get a solution?

@Emily Pascas not yet. Netsuite support is reviewing and considering reporting this as a defect. I'll update this thread if I am able to find a solution.

@bbeach @Emily Pascas did y’all get this resolved? I had the same problem last month and got it fixed, but I can’t remember what I did (partially because we’ve had a lot of issues with dev tools recently, so everything has run together). But if it’s still broken I’ll go review some things and let you know.

@Melissa no we still have the issue. If you are able share what corrected it for you, that would be a much appreciated.

@Melissa Thank you, that would be greatly appreciated!

@Emily Pascas not sure if you have resolved your issue. But as an update this is what resolved it for us: In \ns_npm_repository\oauth1\index.js change line ~125 from:

var hostnameStep1 = this.vm ? hostName : "rest" + molecule + ".<http://netsuite.com|netsuite.com>";

to:

var hostnameStep1 = this.vm ? hostName : "system" + molecule + ".<http://netsuite.com|netsuite.com>";

Then, run this command: npm i oauth1 In our case we had made changes to that file, but without running the install command for oauth1 again, they were not applied. Hope this helps.