Parser failure on name: Antlr exception trace: line 15:7: unexpected char: '#'

• Key: DIRSERVER-381
• Type: Bug
• Status: Closed
• Resolution: Invalid
• Priority: Major
• Assignee: Alex Karasulu
• Reporter: Nick Faiz

Description

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: [e-mail]
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

Comments

[Alex Karasulu]

<biv> hey aok - is it possible to have DIREVE-165 edited to have a more readable title? Can you get rid of the leading 'searchFilter for 2 '? I dont have the editissue perm.<biv> hey aok - is it possible to have DIREVE-165 edited to have a more readable title? Can you get rid of the leading 'searchFilter for 2 '? I dont have the editissue perm.
<aok> ok let me look
<biv> tnx
<aok> ok let me look
<biv> tnx

[Alex Karasulu]

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.

[Emmanuel Lecharny]

Closing all issues created in 2005 and before which are marked resolved