Authentication Errors

Error Message	Scenario	Solution
Secure storage is inaccessible. Ensure that the secure storage in your system is properly configured and accessible.	The OS secure storage isn't accessible. It might be locked or not set up right.	Check the OS-based secure storage service on your machine. For Windows, ensure that Credentials Manager is working. For MacOS, ensure that Keychain is working. For Linux, make sure the default keyring is available and unlocked. You can use Seahorse or another tool that lets you see the GNOME Keyring v2.22+/Libsecret. As a temporary fix, while the secure storage issue is being resolved, you can use the `SUITECLOUD_FALLBACK_PASSKEY` environment variable to set the passkey for the credentials file. If the `credentials_browser_based.p12` file already exists and the passkey from secure storage cannot be retrieved, delete this file and authenticate again to run operations that require authentication. After you re-authenticate, the new credentials file will be saved with the new passkey you set in `SUITECLOUD_FALLBACK_PASSKEY`. For more information, see Browser-Based Authentication Standard Process and Fallback Mode and Setting Up Environment Variables for SuiteCloud SDK Tools.
Secure storage is inaccessible. Ensure that the secure storage in your system is properly configured and accessible.	Secure storage isn't accessible in a CI/CD environment. Actions that need credentials (like deploy) fail with this error because the right environment variables aren't set up to use the credentials in the credentials_ci.p12 file.	Ensure that the following environment variables are set: `SUITECLOUD_CI`=1 `SUITECLOUD_CI_PASSKEY` set to an alphanumeric string with 32-100 characters. With these environment variables set, actions that need credentials (like deploy) can access the auth IDs stored in the `credentials_ci.p12` file. For more information, see Execution Context for Secure Credentials Storage.
There was an error with the private key used to authenticate. The private key does not match the certificate ID <certificateId >.	When you're using machine-to-machine authentication, the private key and certificate ID you entered don't match.	Ensure that you're using the right private key and certificate ID together.
There was an error with the private key used to authenticate. Verify the contents of the private key.	When you're using machine-to-machine authentication, the private key file you specified is either corrupted or not valid.	Generate a new certificate. For information about how to obtain the certificate ID, see OAuth 2.0 Authentication for SuiteCloud SDK.
There was an error with the certificate ID used to authenticate. Verify that certificate ID <certificateId> is valid and not expired or revoked in account <accountId>.	When you're using machine-to-machine authentication, the certificate ID you specified is not valid.	Ensure that OAuth 2.0 is enabled in your account. For more information, see Enable the OAuth 2.0 Feature. Verify that the certificate ID is valid. In your NetSuite account, go to Setup > Integration > Manage Authentication > OAuth 2.0 Client Credentials (M2M) Setup.

Error Message

Scenario

Solution

Secure storage is inaccessible. Ensure that the secure storage in your system is properly configured and accessible.

The OS secure storage isn't accessible. It might be locked or not set up right.

Check the OS-based secure storage service on your machine.

For Windows, ensure that Credentials Manager is working.
For MacOS, ensure that Keychain is working.
For Linux, make sure the default keyring is available and unlocked. You can use Seahorse or another tool that lets you see the GNOME Keyring v2.22+/Libsecret.

As a temporary fix, while the secure storage issue is being resolved, you can use the SUITECLOUD_FALLBACK_PASSKEY environment variable to set the passkey for the credentials file.

If the credentials_browser_based.p12 file already exists and the passkey from secure storage cannot be retrieved, delete this file and authenticate again to run operations that require authentication. After you re-authenticate, the new credentials file will be saved with the new passkey you set in SUITECLOUD_FALLBACK_PASSKEY.

For more information, see Browser-Based Authentication Standard Process and Fallback Mode and Setting Up Environment Variables for SuiteCloud SDK Tools.

Secure storage is inaccessible. Ensure that the secure storage in your system is properly configured and accessible.

Secure storage isn't accessible in a CI/CD environment.

Actions that need credentials (like deploy) fail with this error because the right environment variables aren't set up to use the credentials in the credentials_ci.p12 file.

Ensure that the following environment variables are set:

SUITECLOUD_CI=1
SUITECLOUD_CI_PASSKEY set to an alphanumeric string with 32-100 characters.

With these environment variables set, actions that need credentials (like deploy) can access the auth IDs stored in the credentials_ci.p12 file.

For more information, see Execution Context for Secure Credentials Storage.

There was an error with the private key used to authenticate.

The private key does not match the certificate ID <certificateId >.

When you're using machine-to-machine authentication, the private key and certificate ID you entered don't match.

Ensure that you're using the right private key and certificate ID together.

There was an error with the private key used to authenticate. Verify the contents of the private key.

When you're using machine-to-machine authentication, the private key file you specified is either corrupted or not valid.

Generate a new certificate. For information about how to obtain the certificate ID, see OAuth 2.0 Authentication for SuiteCloud SDK.

There was an error with the certificate ID used to authenticate.

Verify that certificate ID <certificateId> is valid and not expired or revoked in account <accountId>.

When you're using machine-to-machine authentication, the certificate ID you specified is not valid.

Ensure that OAuth 2.0 is enabled in your account. For more information, see Enable the OAuth 2.0 Feature.

Verify that the certificate ID is valid. In your NetSuite account, go to Setup > Integration > Manage Authentication > OAuth 2.0 Client Credentials (M2M) Setup.

Related Topics