![]() But a user can now have different TeamCity username, LDAP username and Windows domain username.The administrator has to specify the user's LDAP/NT username on his/her profile page to make the user be able to login via LDAP/NT authentication. This means that users and their settings remain the same after changing TeamCity server authentication modules if their usernames are the same in the old and new authentication modules. TeamCity maintains a common user list shared among all the authentication modules. ![]() The TeamCity administrator can modify the authentication settings for every user on their profile page. If you are not prompted for the administrator account, please refer to How To Retrieve Administrator Password for a resolution. The very first time TeamCity server starts with no users (and no administrator) so you will be prompted for the administrator account. Use the properties available for modules by selecting/deselecting checkboxes in the Add Module dialog.Īlso, TeamCity plugins can provide additional authentication modules. Switch to advanced mode with the corresponding link on the Administration | Authentication page.Ĭlick Add Module and select a module from the drop-down. The recommended approach is to configure LDAP Integration for your internal employees first and then to add Built-in authentication for external users. ![]() It is possible to use a combination of internal and external authentication. If one of them authenticates the user, the login will be successful if all of them fail, the user will not be able to log into TeamCity. When a user attempts to log in, all the modules will be tried one by one. TeamCity allows enabling several authentication modules simultaneously using the advanced mode in the TeamCity Web UI. Microsoft Windows Domain ( Basic HTTP and NTLM) The following presets are available:ĭefault ( built-in authentication - Basic HTTP) button, select one of the options and Save your changes. To override the existing authentication settings, use the Load preset. Simple mode (default) allows you to select presets created for the most common use cases. The detailed description is available in the previous documentation version. For more options, switch to the Advanced mode.Īny changes made to authentication in the UI will be reflected in the /config/auth-config.xml file, which can be used to configure authentication if editing via the Web UI is not suitable for some reason. To switch to a different preconfigured scheme, use the Load preset button. To modify the existing settings, click the Edit link in the table next to the description of the enabled authentication module. When you first log in to TeamCity, the default authentication including the Built-in and Basic HTTP Authentication modules is enabled and editing authentication settings in the simple mode is active. If you are using JetBrains Hub, you can configure single sign-on (SSO) via JetBrains Hub from TeamCity login form and IDE using a separate plugin for TeamCity. The presets are combinations of authentication modules supported by TeamCity: three credentials authentication modules and two HTTP authentication modules: TeamCity provides several preconfigured authentication options (presets) to cover the most common use-case described below. TeamCity can authenticate users via an internal database, or can integrate into your system and use external authentication sources such as Windows Domain or LDAP.Īuthentication is configured on the Administration | Authentication page the currently used authentication modules are also displayed here.
0 Comments
Leave a Reply. |