Integrate with Oracle NetSuite

1. Enter the following URL in a browser as provided in the example.

   Example:

   https://<host name> /app/login/oauth2/authorize.nl?redirect_uri={callback}&response_type=code&scope=restlets+rest_webservices&state=ykv2XLx1BpT5Q0F3MRPHb94j&client_id={ConsumerKey}.

   Replace {ConsumerKey} with your Consumer key / Client id and {callback} with your redirect URI. The URL above includes the signature scope required for the eSignature REST API.

   This URL opens the Oracle NetSuite authentication screen.

2. After you enter your Oracle NetSuite account email address and password and give consent for the requested scopes and then once you redirect to the login Browser Enter the user Credentials to Login and authenticate then Click on the Continue to allow Oracle NetSuite to access your information to Provide the code. The browser will redirect to your redirect URI with a long string returned for the code parameter embedded in the URL.

   Request:

   https://<host name>/app/login/oauth2/authorize.nl?redirect_uri=http://example.com&response_type=code&scope=restlets+rest_webservices&state=ykv2XLx1BpT5Q0F3MRPHb94j&client_id=7e1c238e-xxxx-xxxx-xxxx-abcea08a3171

   Response: https://example.com/?state=ykv2XLx1BpT5Q0F3MRPHb94j&role=3&entity=4622&company=TSTDRVXXXXXX&code=096835b6aced….......457b00e3c

1. To request a refresh token, send a POST request containing your authorization code to the NetSuite authentication service.
2. Paste the values of Consumer Key and Consumer secret key as User name and Password respectively under Authorization in the Refresh token request with the type as Basic Auth in Postman.
3. In addition, the refresh token request contains a set of body parameters namely grant_type and code.
   1. Update the key as code with value <code>.
      Note
      
      <code> is nothing but the authorization code that you received from the callback in step 1.

      For example, code=096835b6aced..........457b00e3c.

   2. Similarly, update one or more body parameter with the key as grant_type and value as authorization_code and another body parameter with key as redirect_uri and value as the same provided in the step 1.
4. Execute the Authorize Code Grant Refresh Token request to generate an access token and a refresh token.
   1. In the response, you will get elements, namely, access_token, token_type, refresh_token, and expires_in.
   2. Copy/save the values of refresh_token.

   For more information about how to get a refresh token with Auth Code Grant, see NetSuite Applications Suite.

   Examples:

   Request:

   curl --location --request POST " https://<host name>/services/rest/auth/oauth2/v1/token"--header "Authorization: Basic N2UxYzIzOGU1Zj........GI3Njg3MzMzMTZm" --header "Content-Type: application/x-www-form-urlencoded" --data-urlencode "code=34e8dec4289........a52fe26" --data-urlencode "redirect_uri=https://example.com" --data-urlencode "grant_type=authorization_code"

   Response:

   { "access_token":"eyJ0eXAi......mX9f7k1g", "token_type":"Bearer", "refresh_token":"eyJ0eXAi......mruC5c3A", "expires_in":3600 }

   Required element for OAuth2.0 authentication

   Element	Description
   refresh_token	A token that is used to obtain a new access token without requiring user consent and Use this token in the Authorization header of all NetSuite API calls. Providing Values for NetSuite Connector Basic Configuration. After you have obtained the refresh_token value, you must provide these values in authToken under NetSuite Connector basic configuration. For information about configuration, see Configuring the NetSuite Connector. For example, eyJ0eXAi......mX9f7k1g
   refresh_token value	The full refresh token value that is received from authentication.

• This is the authoritative source for my identities

  Select one of the following:

  • Source of identities and their attributes: System acts as a source identities and associated attributes. New identities are created through this option .
  • Source of identity attributes only: System ingests additional identity attributes details and apply to existing identities. This option doesn't ingest or creates new identity records.
• I want to manage permissions for this system

• User
• User manager

1. Select what to do with accounts when early termination begins: Choose the action to perform when an early termination begins. This happens when you need to revoke identity accesses before official termination date.
   • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
     Note
     
     If specific orchestrated system doesn't support the action, no action is taken.
   • Disable: Disables all accounts and disables permissions managed by Oracle Access Governance.
     • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
   • No action: No action is taken when an identity is flagged for early termination by Oracle Access Governance.
2. Select what to do with accounts on the termination date: Select the action to perform during official termination. This happens when you need to revoke identity accesses on the official termination date.
   • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
     Note
     
     If specific orchestrated system doesn't support Delete action, then no action is taken.
   • Disable: Disables all accounts and disables permissions managed by Oracle Access Governance.
     • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
     Note
     
     If specific orchestrated system doesn't support the Disable action, then account is deleted.
   • No action: No action is taken on accounts and permissions by Oracle Access Governance.

Select one of the following actions for the account:

• Delete: Delete all accounts and permissions managed by Oracle Access Governance.
• Disable: Disable all accounts and mark permissions as inactive.
  • Delete the permissions for disabled accounts: Delete directly assigned and policy-granted permissions during account disablement to ensure zero residual access.
• No action: Take no action when an identity leaves the organization.

• Delete
• Disable
• No action