Custom Authentication Options for OAuth 2.0 Credentials

Integration managers have two optional features available for OAuth 2.0 based credentials to connect with systems that don't follow OAuth standards for the way they return an access token or in the way they expect the authorization header to be supplied. The first is a unique authorization token over the supplied OneTrust default, with the second ability to list your own key value pair as custom request headers. These details are never stored with OneTrust.

Note:

Advanced Options for OAuth 2.0 credentials are currently under preview. Please contact OneTrust Support to submit a request for early access.

To provide Authorization Token Value

  1. On the Integration menu, select Credentials.

    The Credentials screen appears.

  2. Create a new credential or select an existing credential that is defined with the following:

    • Web App as Connector Type

    • OAuth 2 as Auth Type

    • Any Grant Type can be used

  3. Open the Advanced Options arrow to reveal the additional fields.
  4. Enter your Authorization Token Value in the first field. Any value provided will overwrite the standard access_token which is normally used for requests. This value should begin tokenValue and be period delimited (.) between each object in the JSON.

    For example, if the POST call to retrieve your custom authentication token returns this JSON payload where sessionId contains the value needed for Access Token.

    JSON 
    {
"requestObject": {
"sessionId": "sampleGuid"
}
}

Token Value should be: ${(tokenValue.requestObject.sessionId)}{{"accessToken"."sample"}}


  5. Click the Save button.

To provide Custom Authorization Request Headers

  1. On the Integration menu, select Credentials.

    The Credentials screen appears.

  2. Create a new credential or select an existing credential that is defined as:

    • Web App as Connector Type

    • OAuth 2 as Auth Type

    • Any Grant Type can be used

  3. Open the Advanced Options arrow to reveal the additional fields.
  4. Enter your details for the Custom Authentication Request Headers for the Key and Value fields. Any supplied Key/Value will overwrite the standard Authorization: Bearer {{accesstoken}} header on the workflow request

    The value <access token> is a pointer to the Access Token field on the credential, it's not recommended to change. The value should be used as a reference to where the token value will appear in the desired header.



  5. Click the Save button.