-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 6.2.1
-
Component/s: User Management, Crowd & LDAP integration
-
Severity 2 - Major
Steps to Reproduce
- Configure Bamboo with LDAP
- atlassian-user-custom.xml
<!-- LDAP repository --> <ldap key="myLdapRepository" name="myActiveDirectory" cache="true"> ... <!-- Default bamboo user repository --> <hibernate name="Hibernate Repository" key="hibernateRepository" description="Hibernate Repository" cache="true"/>
- Make sure at least one group inside LDAP matches a local group in Bamboo (e.g. bamboo-admin)
- Check if the Groups field at http://localhost:8085/bamboo/admin/user/editUser.action?username=<USER> is showing the groups this user has
Expected Results
It shows the groups like when other user repositories are used (Crowd, JIRA, Local)
Actual Results
When editing the user there is no group listed
They do not show up for LDAP nor local users when LDAP is enabled.
Notes
If none of the groups inside LDAP matches at least one local group in Bamboo, it's possible to at least add and edit the local groups that users belong to. It takes one group, if there's a single match between the internal user repository and LDAP, users are unable to edit membership with local groups.
- mentioned in
-
Page Loading...