Error : Machine-to-machine authentication is not a...
# sdfs
shree sashti
08/25/2025, 9:48 AMError : Machine-to-machine authentication is not allowed for the current execution context.
I am getting this error when im trying to authenticate using node cli commands in the mac terminal
This is sdf cmd ive used :
suitecloud account:setup:ci --authid SB3_M2M --certificateid ouoVREScQPsGq-fsdfhodsofnvosdnvo --privatekeypath "/Users/shreesashti.lk/Documents/SDF/Authentication Files/SB3" --account 3822968_SB3j
Jonathan MacKenzie
08/25/2025, 4:27 PMyou have the
SUITECLOUD_CISUITECLOUD_CI_PASSKEYs
shree sashti
08/26/2025, 2:20 PMHi Jonathan ,. thanks for pointing that out . I tried with the same .
this time i got this error :
The following environment variables are currently set: SUITECLOUD_CI, SUITECLOUD_CI_PASSKEYThe operation you are trying to perform is not allowed with the current environment variable configuration.For more information, see <https://system.netsuite.com/app/help/helpcenter.nl?fid=article_0113125121.html>.shree sashti
08/26/2025, 2:21 PMIve set
SUITECLOUD_CI_PASSKEY=qwertyuiopasdfghjklzxcvbn1234567890;
SUITECLOUD_CI =1
m
Marcos Lopez
08/31/2025, 8:21 PMMaybe you need to export those vars like this
export SUITECLOUD_CI_PASSKEY=qwertyuiopasdfghjklzxcvbn1234567890;
export SUITECLOUD_CI =1
j
Jonathan MacKenzie
09/02/2025, 1:26 PMis the "operation you are trying to perform" the same? browser-based authentication (ie
account:setupaccount:setup:cis
shree sashti
09/08/2025, 2:43 PMYes i tried with accountsetupci and set the evironment variables as suggested here. now i able to bypass the error .
Thanks @Jonathan MacKenzie, @Marcos Lopez
shree sashti
09/08/2025, 2:50 PMNow i m stuck this :
There was an error with the private key used to authenticate. Verify the contents of the private key.There was an error with the certificate ID used to authenticate.suitecloud account:setup:ci --authid sb3 --certificateid akjsdfajrRANDOMjfbarkfj --privatekeypath /Users/shreesashti.lk/Documents/SDF/Authentication_Files/SB3/private.pem --account 123456_SB3shree sashti
09/08/2025, 2:51 PMNote : i read somewhere i had to use the "SuiteCloud Development Integration" integration record rather using my own integration record to create the certificate.
Still got the
There was an error with the private key used to authenticate. Verify the contents of the private key.j
Jonathan MacKenzie
09/08/2025, 2:54 PMa few people have been unable to get EC keys working and will get that "error with the private key" error unless an RSA key is used, the third example on that page you linked. the error you got with the RSA key looks like it got further so i think that's the case with you here too. not sure why it's not liking your certificate though, i assume the
akjsdfajrRANDOMjfbarkfjs
shree sashti
09/08/2025, 2:56 PMhi @Jonathan MacKenzie, thanks for the response . THe
akjsdfajrRANDOMjfbarkfjm
Marcos Lopez
09/08/2025, 2:59 PMi did have the same issue using the rsa command suggested in documentation, instead i used this to generate my keys:
openssl req -x509 -newkey rsa:4096 -sha256 -keyout private-key.pem -out certificate.pem -nodes -days 365s
shree sashti
09/08/2025, 3:07 PMThanks @Marcos Lopez for the input , let me try out these and get back.
shree sashti
09/08/2025, 4:05 PMPerfect . It worked 🫡. @Marcos Lopez thanks. your openssl worked .
🙌 1
a
Amruth T A
09/09/2025, 10:53 AMI did the same as suggested in the above pic.but i got a new error while authenticating with CI, "server error. Verify the argumens of the command and that the account gad the following features enabled: OAuth 2.0 and Suite cloud Development Framework"
s
shree sashti
09/09/2025, 4:35 PMIs setting domain a mandatory parameter in setting up the account?
If yes what is the value that to be passed?
7 Views