# Integrating SailPoint with TeamCity

TeamCity is a continuous integration and continuous delivery (CI/CD) platform from JetBrains. Use the TeamCity connector to aggregate users as accounts, groups and roles as entitlements, and access tokens and SSH keys as non-human identities.

The connector is read-only and does not provision access.

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

| Feature | Description |
| --- | --- |
| Test connection | Validates the TeamCity REST API URL and authenticates with the configured username and password. |
| Account aggregation | Aggregates TeamCity users as SailPoint accounts. |
| Account read | Reads a TeamCity user by ID. |
| Entitlement aggregation | Aggregates TeamCity groups and roles as entitlements. |
| Entitlement read | Reads a TeamCity group or role by its identifier. |
| Dataset aggregation | Aggregates TeamCity access tokens and SSH keys as credentials. |

### Non-Human Identity Discovery

- Aggregate TeamCity access tokens and SSH keys

Refer to Dataset Management for more information.

Refer to [Discovering Potential Non-Human Accounts](<https://documentation.sailpoint.com/saas/help/agentic_fabric/nhi/non_human_accounts.html#discovering-potential-non-human-accounts>) for more information.

## Supported Version

The connector targets the TeamCity REST API at `{baseUrl}/app/rest`.

- **TeamCity Cloud** - Hosted accounts, such as `https://your-account.teamcity.com`.

The connector is compatible with TeamCity 2021.1 and later, which supports the REST API v2 format used by this connector.

## Prerequisites

### Preparing TeamCity

Complete these tasks before you configure the TeamCity source.

1. Ensure your TeamCity instance is available to SailPoint over HTTPS.
2. Sign in to TeamCity as a system administrator.
3. Go to **Administration** \> **Users**.
4. Select **Create user account**.
5. Enter a username and strong password for a dedicated SailPoint service account.
6. Assign the **System Administrator** role to the service account at the project root level.
7. Store the username and password in your secrets tooling.

> [!IMPORTANT]
>
> The connector uses HTTP Basic authentication. The service account must be able to read users, groups, roles, access tokens, and SSH keys across the TeamCity instance.

## Required Permissions

An account with the **System Administrator** role satisfies all permissions required by this connector, including reading users, groups, roles, access tokens, and project SSH keys.