Set up a TeamCity connector

ConductorOne provides identity governance and just-in-time provisioning for TeamCity. Integrate your TeamCity instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts	✅	✅
Groups	✅	✅
Projects	✅	✅

The TeamCity connector supports automatic account provisioning.

Gather TeamCity credentials

Each setup method requires you to pass in credentials generated in TeamCity. Gather these credentials before you move on.

A user with the System administrator role in TeamCity must perform this task.

Generate an access token

Log into TeamCity and navigate to Access Tokens in your user profile.
Click Create access token.
Give the token a name, such as “ConductorOne”.
Set the Permission scope to Same as current user.
Click Create. The new token is generated
Carefully copy and save the access token.

That’s it! Next, move on to the connector configuration instructions.

Configure the TeamCity connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of TeamCity credentials generated by following the instructions above

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for TeamCity and click Add.
Don’t see the TeamCity connector? Reach out to support@conductorone.com to add TeamCity to your Connectors page.
Choose how to set up the new TeamCity connector:
- Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Paste your access token in the TeamCity access token field.
Enter your TeamCity instance URL in the next field.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your TeamCity connector is now pulling access data into ConductorOne.

Follow these instructions to use the TeamCity connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Configure the TeamCity connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new TeamCity connector:
- Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your TeamCity connector deployment:

Secrets configuration

# baton-teamcity-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-teamcity-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # TeamCity credentials
  BATON_ACCESS_TOKEN: <TeamCity access token>
  BATON_INSTANCE_URL: <TeamCity instance URL>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-teamcity.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-teamcity
  labels:
    app: baton-teamcity
spec:
  selector:
    matchLabels:
      app: baton-teamcity
  template:
    metadata:
      labels:
        app: baton-teamcity
        baton: true
        baton-app: teamcity
    spec:
      containers:
      - name: baton-teamcity
        image: ghcr.io/conductorone/baton-teamcity:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-teamcity-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the TeamCity connector to. TeamCity data should be found on the Entitlements and Accounts tabs.

That’s it! Your TeamCity connector is now pulling access data into ConductorOne.