Connect to CMDB Using OAuth 2.0 Apps

Use Salesforce OAuth 2.0 applications to give external tools, scripts, and integrations authenticated access to the Cloudaware CMDB API.

This section covers Salesforce External Client Apps and legacy Connected Apps, including OAuth scopes, execution policies, credentials, certificates, and token requests.

Choose an OAuth Flow

Select a flow based on how the integration authenticates and whether you are creating a new application or maintaining an existing configuration.

Use case	Recommended guide
The integration must authenticate with a certificate and private key instead of storing a client secret	JWT Bearer Flow
A server-to-server integration can authenticate with a client ID and client secret as a designated Cloudaware user	Client Credentials Flow
An existing integration already uses a Salesforce Connected App	Connected App Client Credentials Flow (Legacy)

General Configuration Flow

The exact steps depend on the selected OAuth flow, but the general process is:

1. Create an External Client App or identify an existing Connected App.
2. Enable the required OAuth settings.
3. Assign the minimum required OAuth scopes.
4. Configure the running user or certificate-based authentication.
5. Apply the required application policies and permissions.
6. Obtain the client ID and any required client secret or certificate.
7. Request an OAuth access token.
8. Test access with a limited CMDB API request.
9. Store credentials securely and establish a rotation procedure.

Related

For more details, review Salesforce documentation on:

• OAuth 2.0 Client Credentials Flow for Server-to-Server Integration
• OAuth 2.0 JWT Bearer Flow for Server-to-Server Integration