free for TeamCity Professional and TeamCity Enterprise servers users, closed-source
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|
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.
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.
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.
Using the Administration | Hub Settings| Synchronization tab of the server settings, you can enable, configure and run on-demand user synchronization.
TeamCity supports one-way synchronization with Hub: the data is retrieved from Hub and is stored in the TeamCity database. Periodically, TeamCity fetches data from Hub and updates users in TeamCity.
Synchronization with Hub in TeamCity allows you to:
The following options are available:
|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|
Clicking Synchronize now launches synchronization manually. After the synchronization is finished, the results will be reported on the page.
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
Hub dashboard retrieves data from TeamCity with help of TeamCity REST API. As such CORS should be configured on the TeamCity side. The following TeamCity internal properties should be set:
rest.cors.optionsRequest.allowUnauthorized=true rest.cors.origins=<dashboard hostname>
Where <dashboard hostname> should be hostname with protocol and port, for example: http://myinternalwebpage.org.com:8080
You need to restart TeamCity server after changing rest.cors.optionsRequest.allowUnauthorized internal property.
In active development.
Everyone is encouraged to try the plugin, however issues can be uncovered.
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