---
title: Cofense Triage
slug: authentication-guides/cofense-triage
docTags: 
createdAt: 2026-04-28T10:11:27.237Z
---

# Introduction

This guide tells you how to authenticate the Cofense Triage connector in Swimlane using OAuth 2.0 Client Credentials.

You will generate API credentials in Cofense Triage, collect required identifiers, and configure the connector in Swimlane.

# Prerequisites

## Cofense Triage Access Requirements

You must have access to:

- Cofense Triage platform (with administrative privileges)
- API access enabled for your account
- Permission to generate API tokens and OAuth credentials

### Required Credentials

During setup, you will collect:

- URL (Cofense Triage API endpoint)
- Client ID
- Client Secret
- API Token (generated in Cofense Triage)

# Cofense Triage Setup

### Take the following steps to generate an API Token:

1. Log in to the Cofense Triage platform.
2. Navigate to:
   **Administration → Account Management → Operators**
3. Locate the superuser account that will be used for API access.
4. In the **API Token Actions** column, click the **(+) icon**.
5. Copy the generated API token and store it securely.

This token will be used along with your account credentials for authentication.

### Take the following steps to obtain OAuth Credentials:

1. Ensure your application is registered with Cofense Triage.
2. Retrieve the following from your Cofense environment:
   - **Client ID**
   - **Client Secret**
3. Confirm API access is enabled for your account.

### API Endpoint Format

The general Cofense Triage API URL format is: https\://\<hostname>/api/public/v2/

Example: https\://your-instance/api/public/v2/reports

# Connector configuration in Swimlane

1. Log in to Turbine.
2. From the left-hand navigation pane, click **ORCHESTRATION** and click **Assets**.
3. Asset homepage opens.
4. Click the plus icon to open the Configure your Connector Asset window.
5. Select **Cofense Triage** from the Asset type list.
6. Fill in the Asset Settings and Asset Input as shown:

### Configuration - OAuth 2.0 Client Credentials

| **Field**      | **Description**                 | **Required/Optional** |
| -------------- | ------------------------------- | --------------------- |
| url            | Cofense Triage API base URL     | Required              |
| client\_id     | Client ID from Cofense          | Required              |
| client\_secret | Client Secret from Cofense      | Required              |
| verify\_ssl    | Enable/Disable SSL Verification | Optional              |
| http\_proxy    | Optional proxy configuration    | Optional              |

Fields with \* marks are required.

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/lAgluQQ577Km7iHmjKeNm_.blob)

![]()

# Troubleshooting

If authentication fails:

- Ensure the **API token is valid and active**
- Verify **Client ID and Client Secret are correct**
- Confirm the **API base URL is correct**
- Ensure your account has **API access permissions**
- Check for **network/proxy restrictions**
- Verify SSL settings if connection issues occur

You have successfully authenticated the Cofense Triage Connector in Swimlane.

**Sources**

- Cofense Triage API Documentation : [https://community.cofense.com](https://community.cofense.com)