What happens to current HGLab users if I setup LDAP integration?
I currently have a fully functional HgLab with 22 (mostly remote) accounts. I like the idea of having 1 location to manage all accounts and project access from AD, but I think I might be setting myself up for pain. Our current remote/local user mix is 20/2 and of the remote users, we have 2 project managers that help assign new devs to teams, etc. This change would require creating 20 new accounts in AD.
If I create these dev accounts in Active Directory would it be possible to merge the history they've established in HgLab?
If merging them is possible, how can I:
...delegate project manager access?
...use AD groups to manage project access/team members?
With that, I understand I might be making my life difficult upfront, but if we increase the number of devs beyond 30, this might be worthwhile. We also use JIRA for managing tasks and handle users in the same fashion above. Fortunately they also offer LDAP integration so this may be required if we do grow in the future.
Thanks for your time :).
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Anton Gogolev on 02 Feb, 2015 08:54 PM
Nic,
The way LDAP integration currently works is it basically "steals" whatever
user accounts were previously registered under a given email and makes them
LDAP accounts.
In other words, if there is an account for, say, "[email blocked]" and
you add an LDAP account for the same email address, whenever Dilbert signs
in into HgLab, this existing account will get become bound to the LDAP
"catalog" and all commits and pushes will remain untouched.