[ http://issues.apache.org/jira/browse/DIREVE-165?page=all ]
Alex Karasulu resolved DIREVE-165:
----------------------------------
Fix Version: 0.9.2
Resolution: Invalid
This is not a bug. You are incorrectly using the member attribute. According
to 2256 this is the following definition for a member attribute:
attributetype ( 2.5.4.31 NAME 'member'
DESC 'RFC2256: member of a group'
SUP distinguishedName )
Notice that member values must be distinguished names. So your LDIF is invalid
since the member values are not correctt distinguished names. The server
basically chokes trying to read a DN for groupB in this incorrect filter of
(member=groupB). If you used the proper values in the LDAP for the member
attribute the following filter would work:
(member=cn=groupB,ou=groups,ou=system)
Once I fixed the LDIF and ran this search filter it all worked like a champion.
> Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'
> ------------------------------------------------------------------------------
>
> Key: DIREVE-165
> URL: http://issues.apache.org/jira/browse/DIREVE-165
> Project: Directory Server
> Type: Bug
> Versions: 0.9.1
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
> Fix For: 0.9.2
> Attachments: test-userbase.ldif
>
> This probably only occurs under a certain config. (see below), so it is
> possible that the configuration itself is erroneous.
> When running a search on a user, represented in LDIF, below, I hit the
> following stack trace with the following search filter:
> search filter: (member=groupB)
> Parser failure on name:
> groupB
> Antlr exception trace:
> line 15:7: unexpected char: '#'
> at
> org.apache.ldap.common.name.antlrTypeLexer.nextToken(antlrTypeLexer.java:147)
> at antlr.TokenStreamSelector.nextToken(TokenStreamSelector.java:64)
> at antlr.TokenBuffer.fill(TokenBuffer.java:69)
> at antlr.TokenBuffer.LA(TokenBuffer.java:80)
> at antlr.LLkParser.LA(LLkParser.java:52)
> at antlr.Parser.match(Parser.java:212)
> at
> org.apache.ldap.common.name.antlrNameParser.attributeTypeAndValue(antlrNameParser.java:179)
> dn: uid=ldapusera,ou=users,ou=system
> cn: ldapusera
> sn: Surname1
> givenname: ldapusera
> objectclass: top
> objectclass: person
> objectclass: organizationalPerson
> objectclass: inetOrgPerson
> ou: Human Resources
> ou: People
> l: Atlassian test subject
> uid: ldapusera
> mail: [EMAIL PROTECTED]
> userpassword: passa
> title: groupA
> title: groupB
> member: groupA
> The search filter successfully works on title, uid, and mail. Perhaps I'm
> making a mistake by trying to incorporate the member attribute, from RFC 2256
> (2.5.4.31), into an inetorgperson entity? All the same, the error message is
> mysterious ...
> This problem is occurring on 0.9.1 main, before the addition of the Spring
> config. layer (i.e., Im still setting up with a server.properties file).
> Cheers,
> Nick
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
