-
Bug
-
Resolution: Fixed
-
Low
-
3.6.0
-
None
-
1
-
Severity 3 - Minor
-
2
-
Issue Summary
- If we were to search for a group in uncached connector directory through the "View User -> Groups" view to add in Crowd 3.6 and above, it throws the error below, and we're unable to filter the group.
Exception caught in 500 page LDAP-based membership queries do not support search restrictions.
Steps to Reproduce
- Set up an uncached connector directory in Crowd with multiple groups.
- Try searching for a group via any of the Add groups functionality in Crowd, either via a user's Groups tab, or from the Directory's Options tab.
- The error below will show.
System error A system error has occurred please contact your administrator. If this problem continues to occur please contact Atlassian by opening a support request with the following information: A description of your problem and what you were doing at the time it occurred Cut & paste the error and system information found below Attach the application server log file (if possible). Error information Cause: java.lang.IllegalArgumentException: LDAP-based membership queries do not support search restrictions. Stack trace: java.lang.IllegalArgumentException: LDAP-based membership queries do not support search restrictions.
- If no value is put into the search box, all groups are returned successfully
Expected Results
- The groups we entered into the search box should be returned.
Actual Results
- We hit into the error above.
- The below exception is thrown in the xxxxxxx.log file:
2019-11-13 08:31:54,543 http-nio-8095-exec-24 ERROR [500ErrorPage] Exception caught in 500 page LDAP-based membership queries do not support search restrictions. java.lang.IllegalArgumentException: LDAP-based membership queries do not support search restrictions. at com.atlassian.crowd.directory.SpringLDAPConnector.searchGroupRelationships(SpringLDAPConnector.java:1352) at com.atlassian.crowd.directory.AuditingDirectoryDecorator.searchGroupRelationships(AuditingDirectoryDecorator.java:105)
Workaround
- Currently there is no known workaround for this behavior. A workaround will be added here when available