Skip to main content

​
What Living Security needs

Scopes: Read access to Alerts and Users Required role: Customer Cloud Admin or Security Center User with API Client management permissions

​
Prerequisites

  • You must be signed in to the Code42 console with a role that has permission to manage API Clients.

​
Part A — In Code42

Your Code42 administrator completes these steps.
1

Navigate to API Client Management

  1. Sign in to your Code42 console (e.g., console.us.code42.com).
  2. In the left navigation, click Settings, then select API Clients.
2

Create an API Client

  1. Click Add new API Client.
  2. Enter a descriptive name (e.g., Living Security Platform).
  3. Select the access level that grants read access to Alerts and Users:
In most deployments, the Security Center User role or equivalent read-only role is sufficient.
  1. Click Create.
Grant only the access level needed for read operations. Administrative or write-level permissions are not required.
3

Identify your regional API host

Match your Code42 console URL to the corresponding API host:Enter the host only — no https:// prefix and no trailing slash.
4

Copy and save your credentials

Copy the Client ID and Client secret values and store them securely.
The Code42 console displays the Client secret only once at creation time. If you navigate away without copying it, you must delete the API Client and create a new one.

​
Part B — In the Living Security Platform

The program owner completes this step, or the system admin if using delegated setup.
1
You are now connected to Code42.

​
Troubleshooting

The Client secret may have been rotated, deleted, or expired. Create a new API Client, copy the new credentials, and reconnect the integration.
The API Client lacks read access to Alerts or Users. Create a new API Client with the Security Center User role or equivalent read permissions.
Using the wrong host causes authentication to fail. Verify:
  • US accounts use api.us.code42.com or api.us2.code42.com
  • EU accounts use api.ie.code42.com
  • Gov accounts use api.gov.code42.com
The connection dialog’s API Key field accepts the client secret. The Client ID is handled internally during OAuth2 token exchange.