LDAP: error code 18 - Inappropriate Matching in iManager Simple Selection

  • 7002302
  • 06-Jan-2009
  • 26-Apr-2012

Environment

iManager 2.7
iManager 2.7.2

Situation

In iManager 2.7.0, when using the Simple Selection Search you see two "E-mail address" selections, or what appears to be duplicates.  Which "E-mail address" you choose will determine if your search is successful or not.

In iManager 2.7.0, searching on E-mail address:
One search will actually search on "Internet E-mail address" nds attribute/ mail ldap attribute - this will succeed.
The other will search on "E-mail address" nds attribute / eMailAddress ldap attribute - this will fail.

This has been partially resolved in iManager 2.7.2.  In iManager 2.7.2, the "working" E-mail address search was renamed to the appropriate "Internet E-mail address" This one will succeed.  However the broken "E-Mail address" was left in the drop down for Simple Selection. This option should not be used, as it will fail.

Error from within iManager
[LDAP: error code 18 - Inappropriate Matching]

DSTRACE taken on the iManager Server (broken)
11:19:12 A8368BA0 LDAP: (192.168.2.127:26669)(0x0002:0x63) Search request:
   base: ""
   scope:2 dereference:3 sizelimit:0 timelimit:0 attrsonly:0
   filter: "(&(eMailAddress=b*)(objectClass=User))"
   attribute: "givenName"
   attribute: "SN"
11:19:12 A8368BA0 LDAP: ldap2NDSSearchFilter: substring match used on unsupported syntax
11:19:12 A8368BA0 LDAP: (192.168.2.127:26669)(0x0002:0x63) nds_back_search: ldap2NDSSearchFilter failed with err 18 (0x12)
11:19:12 A8368BA0 LDAP: (192.168.2.127:26669)(0x0002:0x63) Sending operation result 18:"":"" to connection 0xcf3ba00


DSTRACE taken on the iManager Server (working)
11:19:35 A7411BA0 LDAP: (192.168.2.127:26675)(0x0002:0x63) Search request:
   base: ""
   scope:2 dereference:3 sizelimit:0 timelimit:0 attrsonly:0
   filter: "(&(mail=c*)(objectClass=User))"
   attribute: "givenName"
   attribute: "SN"
11:19:35 A7411BA0 LDAP: (192.168.2.127:26675)(0x0002:0x63) Sending operation result 0:"":"" to connection 0xcf3b780

Status

Reported to Engineering