The plugin adds the ability to log in to TeamCity via JetBrains Hub, and allows for synchronization of user details from Hub to TeamCity: creating/deleting TeamCity users and updating TeamCity user data (username, display name, email, jabber, default VCS usernames, etc.).
Creating/deleting TeamCity user groups UpdatingTeamCity user group data (name, description) Assigning/unassiging users/groups to/from groups Merging users/groups Export of TeamCity users/user groups to HubExport of users groups, membership Optional export of user details ( email, jabber, default VCS usernames, built-in password hash, NT/LDAP username)Setting a Hub ID for every exported user/group
The plugin requires TeamCity server to be run with Java version 1.7+. If your TeamCity server uses Java 1.6, the plugin will not be loaded.
|TeamCity version||Download link|
|TeamCity 2018.1.x and later||Download|
Install the plugin as usual.
After the server restart, you can view the enabled Hub authentication on the Administration | Authentication page and manage the integration with Hub using the Administration | Hub Settings page.
The Hub plugin adds two JetBrains Hub authentication modules to TeamCity:
You can view the currently enabled authentication modules on the Administration | Authentication page.
Removing the JetBrains Hub modules will disable authentication via Hub.
If you are using an external provider to authenticate to JetBrains Hub (e.g. GitHub, Google, etc.), you will be able to log in to TeamCity. However, to log in to TeamCity from an IDE, you'll need to add credentials for your JetBrains Hub user (username and password) and use these credentials to authenticate to TeamCity from your IDE.
Enabling / Disabling integration with Hub
On the Administration | Hub Settings page provide the Hub URL of the following format
Сlick Register TeamCity service in Hub.
Note that the Guest user in Hub needs to be allowed (unbanned) for the TeamCity service registration in Hub.
You will be redirected to the Services page in Hub. Verify the TeamCity Hub service using the Trust button.
After you trust the TeamCity service in Hub, return to the TeamCity Web interface to configure user synchronization.
Synchronization with Hub in TeamCity allows you to:
- Retrieve retrieve the user's profile data from Hub
- Automatically automatically create and remove users in TeamCity based on the information retrieved from Hub
|Enable users synchronization||Allows importing users and their details from Hub to TeamCity.|
|Update user profiles in TeamCity||The user name, email and VCS usernames in TeamCity will be updated with data from the user profile in Hub on the first synchronization. If any of this data will be later modified in TeamCity, the changed data will not be imported from Hub on the next synchronization.|
|Create user accounts in TeamCity||New users (those existing in Hub but not existing in TeamCity) matched by the users filter will be imported to TeamCity with their login details, emails and VCS usernames. All the imported users will have a Hub ID in TeamCity. |
If a user with the same name exists in TeamCity and Hub, the user is not synchronized until they login to TeamCity via Hub. The existing TeamCity users with no match in Hub will remain intact.
|Delete user accounts from TeamCity|
If your TeamCity server is available under several URLs (in addition to the URL configured on Administration | Global Settings in TeamCity UI), you will need to add extra URLs manually to the TeamCity service in Hub as valid redirect URLs.For each URL, add "<TeamCity server URL>/hubPlugin/login.html" line
Using 2FA in Hub
If you enable two factor authentication in Hub, you lose ability to login to TeamCity using password (via TeamCity login page or from IDE integration plugins). Since TeamCity 2019.1 you can create and use TeamCity authentication token instead of the password in such cases.
Enabling access to TeamCity for Hub Dashboard
The Hub dashboard retrieves data from TeamCity with help of using the TeamCity REST API. As such CORS should be configured on the TeamCity side. The following TeamCity internal properties should have to be set:
rest.cors.optionsRequest.allowUnauthorized=true rest.cors.origins=<dashboard hostname>
<dashboard hostname> should be is the hostname with the protocol and port, for example: http://myinternalwebpage.org.com:8080
You need to restart TeamCity server after changing the
Plugin Development Status
If you believe you've faced a bug: Issue Tracker (project: TeamCity)
If you want to ask a question or discuss: Forum
Any of the above, but you do not want it to be publicly accessible: Online Form or Feedback email