Create a NetSuite connection to access NetSuite data.
After you create a NetSuite connection, you can validate, test, and save the connection.
You can then publish the NetSuite connection and click the Metadata tab to view the generated process objects for the connection.
You can perform CRUD operations such as create, read, update, and delete on existing tables in NetSuite. To publish a NetSuite connection successfully, you must have sufficient roles to access the data in the table specified in the request.
You get an access token to authorize all the connection requests. After you generate the access token once, you can use it for multiple requests such as create, read, update, and delete records from NetSuite for the duration specified in the client credentials. By default, the access_token is set to 60 minutes.
Setting up a NetSuite instance
Before you set up the NetSuite instance, you must enable OAuth 2.0 and generate and OAuth certificate.
Enable OAuth 2.0
Before using OAuth 2.0, you must enable the feature. Perform the following steps to enable OAuth 2.0:
1Go to Setup > Company > Enable Features.
2Click the SuiteCloud subtab.
3In the Manage Authentication section, agree to the terms for OAuth 2.0.
4Click Save.
Note: The Manage OAuth 2.0 Authorized Applications link is available in the Settings portlet for users with the Log in Using OAuth 2.0 Access Token permission. Users can only list their own authorized applications through this link. Administrators and users with the OAuth 2.0 Authorized Applications Management permission can list all authorized applications in the account at Setup > Users/Roles > OAuth 2.0 Authorized Applications.
After you enable OAuth 2.0, you must set up OAuth roles and create integration records for Applications to use OAuth 2.0. For more information, see the Oracle documentation.
Generate OAuth 2.0 certificate
A certificate for the OAuth 2.0 client credentials flow contains the following keys:
•Public key. An administrator or a user with the OAuth 2.0 Authorized Applications Management permission uploads the public part of the certificate during the client credentials flow mapping process.
•Private key. The private key provides the signature of the JWT token in the POST request to the token endpoint. For more information about POST request to the token endpoint, see the Oracle documentation.
You must ensure that the certificate meets the following requirements:
•The public key is in x.509 format with a file extension of .pem.
•The length of the RSA key must be 3072 bits or 4096 bits.
•The maximum certificate validity is two years. If the certificate is valid for a longer time period, the system automatically shortens the validity to two years.
•One certificate can be used only for one combination of integration record, role, and entity. If you want to use the same integration record for multiple entities or roles, you must use a different certificate for each unique combination.
Perform the following steps to generate the OAuth 2.0 certificate:
