Bug 658307 - LDAP search failed when 'cn' attribute is missing and CN shouldn't be a requirement.
Summary: LDAP search failed when 'cn' attribute is missing and CN shouldn't be a requi...
Alias: None
Product: RHQ Project
Classification: Other
Component: Configuration
Version: 3.0.1
Hardware: All
OS: All
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
Blocks: jon30-bugs
TreeView+ depends on / blocked
Reported: 2010-11-29 23:08 UTC by Roger Hui
Modified: 2018-11-14 16:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-30 20:36:12 UTC

Attachments (Terms of Use)

Description Roger Hui 2010-11-29 23:08:59 UTC
Description of problem:
When the CN attribute is missing the group, JOn is unable to pick up the groups. 

Version-Release number of selected component (if applicable):
JON 2.4.0 

How reproducible:
Create a LDAP group that doesn't contain CN attributes, and run the LDAPTestSettings.jar 

You will see null at the groupFilter.
STEP-3:TESTING: This ldap filter (objectclass=groupOfNames) will be used to locate ALL available LDAP groups
STEP-3:FAIL: There was an error searching with the groupFilter supplied: objectclass=groupOfNames'
Actual results:
Null pointer returned. 

Expected results:
It should be able to return a list of groups. 

Additional info:
There is a workaround, try to modify the 'group filter' entry to have LDAP exclusion logic to hide those groups from the RHQ LDAP search. Ex. &(objectclass=groupOfNames)(!cn='') The only problem with this approach is that this is a large amount of groups.

Comment 1 Roger Hui 2010-11-29 23:10:03 UTC
Here is the case for more details: 00382109
Can we get it fixed in 2.4.1?

Comment 2 Charles Crouch 2011-09-30 17:49:48 UTC
removing superfluous trackers

Note You need to log in before you can comment on or make changes to this bug.