Managing OAuth 2.0 Client Credentials
Today, several security issues and concerns could exist with using a standard API key implementation. OneTrust is committed to providing more secure solutions and supports the OAuth 2.0 authorization framework for a more advanced approach to external application access.
A maximum of 500 OAuth 2.0 client credentials can be created per account.
Using Client Credentials
You can create and manage client credentials that utilize the OAuth 2.0 authorization framework using the Client credentials screen in Global Settings. When creating client credentials, you must be mindful of the organization in which you are creating them given that client credentials are assigned to the organization in which they are created. This means that APIs called using the client credentials will only be able to return objects accessible by the organizational group in which the client credentials were created.
Client credentials that appear on the Client credentials screen also depend on the organization in which you are currently logged in. For example, say your organizational hierarchy contains a root organization named Global and two child organizations named North America and Europe. If you are currently within the Global organization, you will be able to see all client credentials created within the Global, North America, and Europe organizations. However, if you navigate to the North America organization, you will only be able to see client credentials created in the North America organization and will not have visibility into client credentials created in the Europe organization or Global organization.
When viewing client credentials within the root organization, there is currently no way to identify in which organization each client credential was created on the Client credentials screen. However, you can navigate to other sub-organizations to locate specific client credentials to determine in which organization it was created. Alternatively, you can incorporate the organization name within the name of the client credential to help you identify those details in the future.
- Field
- Description
- Name
-
Name of the client credential. Click the link in the Name field to access the Client credential details screen.
- Creation date
-
Date and time that the client credential was created.
- Created by
-
Name of the user who created the client credential.
- Client ID
-
Unique identifier for the client credential.
To create OAuth 2.0 client credentials
To edit a client credential
To upload a mutual authentication certificate
Site Admins can upload a Mutual Transport Layer Security (mTLS) certificate for generated client credentials when using a custom branded URL.
For more information on custom subdomains, see Customizing OneTrust with a Custom Subdomain.
To generate a token
Access tokens are used to authorize applications to access an API. Since API responses can contain user information, access tokens must be kept confidential and secure.
The following procedure details how to generate a token from within Global Settings in the OneTrust application. Alternatively, you can generate a token using the Generate Access Token API in the OneTrust Developer Portal.
To reset the Client Secret details
Client Secrets can be revoked, if necessary. For example, if the Client Secret was unintentionally exposed, you can reset the current Client Secret and download a new Client Secret using the following steps.
Resetting a Client Secret will not invalidate any access tokens. However, any existing integrations that use the old Client Secret will no longer work and will need to be updated.
To delete a client credential
Client credentials can be deleted, if necessary. For example, if all previous access tokens need to be invalidated, you can delete the client credential using the following steps.
Deleting client credentials will invalidate any access tokens. Any existing integrations using the old client credentials will no longer work and will need to be updated.