Authentication Settings

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 4.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 4.x Documentation

Table of Contents

Out-of-the-box TeamCity Enterprise edition supports three authentication schemes:

TeamCity Professional edition only supports TeamCity Default Authentication.

Active authentication scheme is configured in the auth-type section of the main-config.xml file located in the <TeamCity data directory>/config directory, for example:

Authentication type is defined by the login module, welcome message and the possibility to use anonymous login. Built-in login modules are:

  • jetbrains.buildServer.serverSide.impl.auth.DefaultLoginModule for Default Authentication
  • jetbrains.buildServer.serverSide.impl.auth.NTDomainLoginModule for Windows Domain Authentication
  • jetbrains.buildServer.serverSide.impl.auth.LDAPLoginModule for LDAP Authentication
    TeamCity extensibility note
    Any implementation of javax.security.auth.spi.LoginModule can be used, provided it is registered via jetbrains.buildServer.serverSide.auth.LoginModuleDescriptor bean.

Default Authentication

Configuration of <TeamCity data directory>/config/main-config.xml:

Users database is maintained by TeamCity. New users are added by TeamCity administrator (in administration area section) or user are self-registered if <free-registration allowed="true" /> tag is specified.

Windows Domain Authentication

Configuration of <TeamCity data directory>/config/main-config.xml:

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 <username>@<domain> login name syntax is supported. It is also possible to log in using only a username if the domain is specified in ntlm.defaultDomain property of <TeamCity data directory>/config/ntlm-config.properties file.

Windows Domain Authentication on Unix-like Computers

TeamCity supports Windows Domain Authentication on Unix-like computers. For this to work, check the <TeamCity data directory>/config/ntlm-config.properties file and make sure the following line is commented out.

Please refer to the http://jcifs.samba.org/src/docs/api/ page for information about other supported properties.

If you want to use the NT domain authentication available in TeamCity version prior to 3.1, ensure the line ntlm.compatibilityMod=true is present and not commented in the ntlm-config.properties file.

LDAP Authentication

Please refer to the corresponding section.



See Also:

Labels:

authentication authentication Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

1 Comment

comments.show.hide

  1. Mar 04, 2009

    Heikki Rauhala

    Is it possible to change the authentication scheme of a running system?

    I installed teamcity, started up without ldap, then configured LDAP authentication, but could not figure out how to assign the administrator role to an LDAP user that had not yet registered. I had not yet configured too much things, so I just cleaned the database and got an administrator account. However, it would be nice if this page would describe that you have to setup LDAP before you do the initial login, or how to assign the administrator role.