TeamCity On-Premises
 
Get TeamCity On-Premises

Manage Refreshable Access Tokens

Edit pageLast modified: 18 December 2024

In TeamCity, there are multiple entities whose functionality requires accessing VCS hosting providers: VCS roots, Commit Status Publishers, Pull Requests features, and so on. These entities typically offer multiple VCS authentication options:

  • Regular username/login credentials — being the most vulnerable, this authentication method is gradually deprecated by major VCS hosting providers.

  • Personal access tokens (PATs) — issued on the VCS provider's side and then copied into a TeamCity object. These tokens grant the same or fewer permissions as those of the issuing user.

  • Refreshable tokens — personal or non-personal tokens. To acquire this token, TeamCity communicates with a VCS provider using an existing OAuth (or OAuth-like) connection.

This topic explains how to issue, assign, and manage refreshable tokens.