|You are viewing documentation of TeamCity 5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.|
Out-of-the-box TeamCity Enterprise edition supports three authentication schemes:
Switching Authentication Scheme
To switch from one authentication scheme to another you need to edit
Please note that each authentication type maintains own list for users. This means that on switching from one authentication to another you start with no users (and no administrator) and will be prompted for administrator account on first TeamCity start after the authentication change . This also means that all the existing users will need to create their accounts and re-enter their settings anew.
if you are not prompted for administrator account on switching to a new scheme, this means this there are users in the scheme already. If there is no administrator account in this scheme, you can use
Supported values for
Example of the relevant
Users database is maintained by TeamCity. New users are added by TeamCity administrator (in administration area section) or user are self-registered if
Windows Domain Authentication
Windows Domain Authentication is supported if TeamCity server is installed under Windows 2000, Windows XP or Windows Server 2003, as well as under Unix-like OS.
Prior to TeamCity 3.1, all Windows domain users that can log on to the machine running TeamCity server can also log in to TeamCity using the same credentials.
To log in to TeamCity users should provide their user name in the form DOMAIN\user.name and their domain password. Since TeamCity 3.1
Windows Domain Authentication on Unix-like Computers
TeamCity supports Windows Domain Authentication on Unix-like computers. For this to work, check the
Please refer to the "Available Properties" section on http://jcifs.samba.org/src/docs/api/ page for information about other supported properties.
Please refer to the corresponding section.