-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Highest
-
None
-
Affects Version/s: 6.2.2
-
Component/s: User Management, Crowd & LDAP integration
-
Severity 2 - Major
Steps to Reproduce
- Set a Windows Active Directory with MaxPageSize set to 1000
- Make sure the AD has MORE than 1000 users
- Run an LDAP search with filter settings from atlassian-users.xml and save the results
- Enable the following debug in Bamboo - this will show up the filter used to get the results from AD
Classpath com.atlassian.user.impl.ldap Type DEBUG - Try to give permission to a user not returned in step 3
Expected Results
Bamboo is able to find the user and the permission can be assigned
Actual Results
Bamboo only returns the user if he is inside the first 1000 results returned by the default LDAP search. Bamboo runs every time a the same default search, not a restricted search depending on what the user is typing.
Workaround
Reduce the number of users and groups returned using a more restricted LDAP configuration on atlassian-users.xml
Notes
If the number of results is big (not restricted to 1000 - like the scenario, we have when using OpenLDAP, ApacheDS etc) the instance might end up with performance problems: [BAM-18755] Bamboo retrieves all users from LDAP when adding global permissions
If the search is restricted we will lose results as we have in the past:[BAM-18051] Bamboo does not paginate records over MaxPageSize