Red Hat Bugzilla – Bug 652800
Unable to use parentheses in search filters for LDAP configuration
Last modified: 2015-07-30 12:41:16 EDT
Description of problem:
Currently, if parentheses are specified within the Group Search Filter, the LDAP search will return no results. Removing the parentheses results in the correct results being returned.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In LDAP configuration, set Group Search Filter property to below example, or equivalent for the LDAP environment:
No results are returned when attempting to assign LDAP groups to roles .
Expect that LDAP groups would be retrieved in the same manner as when the Group Search Filter does not use parentheses, such as in below example:
It would be nice to be a little more lax in this case since I would expect the extra brackets are ignored by most ldap query tools, and we should aim to act similarly here.
We have hit this now also with JON 3.1.2 and newer versions of Java.
In older versions of Java this failed silently and no groups were returned.
In newer versions, we tested with 1.6.0_45 and 1.7.0_17, Java actually will throw an exception:
ERROR [org.rhq.enterprise.server.resource.group.LdapGroupManagerBean] The ldap group filter defined is invalid
javax.naming.directory.InvalidSearchFilterException: invalid attribute description; remaining name 'dc=jbossuk,dc=redhat,dc=com'
Simeon, any idea of this was ever enhaced?
We have not yet fixed/relaxed this handling. It should just be a matter of checking for brackets and not adding them when they are already there with the underlying query. I suspect the customers would like to add more complicated LDAP group logic here. Currently focused on JON 3.3 so not sure how soon we'll get to this.
This is considered a bug as parenthesis are a standard part of a directory search query. The problem here is that JBoss ON is adding parenthesis when it shouldn't. As comment 5 indicates, the expected behavior here is if no parenthesis are provided by the user/configuration, they get implicitly added.
This looks like a duplicate of BZ 784164, which was fixed. Can someone verify that the bug really exists in JON 3.3?
Verified on JBoss ON 3.3.3 ER01 build and Windows server 2008 active directory.
In LDAP configuration, set Group Search Filter property to (objectclass=group)
The LDAP configuration is saved successfully without exception.
Results are returned while attempting to assign LDAP groups to roles. Also verified that the results filter in available groups is working. Please refer the attached screenshot.
Created attachment 1051704 [details]
Test case added:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.