I'm integrating Bamboo with Active Directory, and found that after the initial bind operation bamboo performs a search using the filter specified in <userSearchFilter> from atlassian-user-custom.xml, BUT on the LDAP searchrequest the filter is modified:
- the file specifies <userSearchFilter>(objectClass=user)</userSearchFilter>
- the operation shows (&(objectClass=user)(sAMAccountName=anonymousUser))
Since there is no account called anonymousUser (and is not the user that is trying the login) the search operation returns with zero values, and the login is rejected. If I try Paddle with the atlassian-user-custom.xml file, the search DOES use the filter specified in the XML file.
Why does bamboo add an extra filter if paddle doesn't? This defeats the purpose of using paddle for testing, if bamboo modifies the search. Also, how can I stop bamboo from adding that "sAMAccountName=anonymousUse" filter? Because of that no domain user can login, while paddle shows that everything is working.
Many thanks!!