# Configuring the TeamCity SaaS Connector

To configure the TeamCity SaaS connector to discover non-human identities, you'll create a service account in TeamCity. This will allow Agentic Fabric to discover access tokens and SSH keys in TeamCity and aggregate them as non-human identities.

!!! important

If your organization has already configured a TeamCity SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

## Creating a Service Account in TeamCity

1. [Create a service account](https://www.jetbrains.com/help/teamcity/cloud/creating-and-managing-users.html#Creating+New+User) in TeamCity. You'll provide the account's username and password in Agentic Fabric to complete the connection.
2. [Assign](https://www.jetbrains.com/help/teamcity/cloud/creating-and-managing-users.html#Assigning+Roles+to+Users) the new account the System Administrator role at the project root level. This role grants read access to all users, groups, roles, tokens, and SSH keys across the server.

## Connecting TeamCity to Agentic Fabric

1. Go to the **Connect Source** step of the Agentic Fabric onboarding experience.
2. Select **TeamCity SaaS** from the left pane.
3. In the **TeamCity SaaS** section, complete the following:

- In the **Source Name** field, enter a unique name for the source.

- In **Source Owner** field, select the identity who will own the source.

- In the **Description** field, enter a unique description for the source to distinguish it from similar connections.

4. In the **Configure Authentication** section, complete the following:

- In the **Base URL** field, enter the base URL of your organization's TeamCity instance (`https://your-account.teamcity.com`) or (`https://teamcity.yourcompany.com`).
      - In the **Username** field, enter the username of the TeamCity service account.
      - In the **Password** field, enter the password of the TeamCity service account.

5. Select **Test Connection** to ensure the connection is successful.

6. If the test is successful, select **Aggregate** to run an aggregation for the source. Select **Exit** to skip this step. You can configure aggregations for the source's [datasets](../../../sources/datasets.md#configuring-dataset-aggregations) later in the source's configuration. For information on the datasets specific to TeamCity, refer to TeamCity's [connector documentation](https://documentation.sailpoint.com/connectors/saas/teamcity/help/saas_connectivity/teamcity/datasets.html).

A **Completed** status is now displayed next to the source in the left panel.

7. Choose another connector to configure or select **Continue** to proceed to the next onboarding step.

Configuring the TeamCity SaaS Connector

To configure the TeamCity SaaS connector to discover non-human identities, you'll create a service account in TeamCity. This will allow Agentic Fabric to discover access tokens and SSH keys in TeamCity and aggregate them as non-human identities.

Important

If your organization has already configured a TeamCity SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

Creating a Service Account in TeamCity

Create a service account in TeamCity. You'll provide the account's username and password in Agentic Fabric to complete the connection.
Assign the new account the System Administrator role at the project root level. This role grants read access to all users, groups, roles, tokens, and SSH keys across the server.

Connecting TeamCity to Agentic Fabric

Go to the Connect Source step of the Agentic Fabric onboarding experience.
Select TeamCity SaaS from the left pane.
In the TeamCity SaaS section, complete the following:
- In the Source Name field, enter a unique name for the source.
- In Source Owner field, select the identity who will own the source.
- In the Description field, enter a unique description for the source to distinguish it from similar connections.
In the Configure Authentication section, complete the following:
- In the Base URL field, enter the base URL of your organization's TeamCity instance (https://your-account.teamcity.com) or (https://teamcity.yourcompany.com).
- In the Username field, enter the username of the TeamCity service account.
- In the Password field, enter the password of the TeamCity service account.
Select Test Connection to ensure the connection is successful.
If the test is successful, select Aggregate to run an aggregation for the source. Select Exit to skip this step. You can configure aggregations for the source's datasets later in the source's configuration. For information on the datasets specific to TeamCity, refer to TeamCity's connector documentation.

A Completed status is now displayed next to the source in the left panel.
Choose another connector to configure or select Continue to proceed to the next onboarding step.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.