![]() ![]() Windows domain authentication module was added and the default one was removed). Then the authentication module was changed to Windows domain authentication (i.e. Let's imagine that the administrator had the "jsmith" TeamCity username and used the default authentication. LDAP Integration allows setting LDAP property to get TeamCity username from user's LDAP entryĬare should be taken when modifying authentication settings: there can be a case when the administrator cannot login after changing authentication modules.The domain account can be edited on the user profile page Windows Domain authentication allows specifying the default domain and assumes the Domain account name is equal to the TeamCity user.Built-in authentication stores a TeamCity-maintained password for each user.Handling of the user mapping by the bundled authentication modules: Authentication modules regularly have a configuration on how to map external user data to a TeamCity user and some (Windows Domain, JetBrains Hub) allow to edit the external user linking data on the TeamCity user profile. This means that a single TeamCity user can authenticate using different modules, provided the entered credentials are mapped to the same TeamCity user. The TeamCity list of users and authentication modules just map external credentials to the users. 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.Click Add Module and select a module from the drop-down.Switch to advanced mode with the corresponding link on the Administration | Authentication page.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. Since TeamCity 10.0.2, if the System Administrator creates users without password with several authentication modes enabled on the server including the Built-in one, and later changes authorization from mixed one to the build-in one, users with no password will be unable to log in to TeamCity. 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).Default ( 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. Any 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |