[imp] LDAP - GWIA

[Craig White]

> -----Original Message-----
> From: Cliff Green [mailto:green@UMDNJ.EDU]
> Sent: Monday, June 25, 2001 11:24 AM
> To: imp@lists.horde.org
> Subject: Re: [imp] LDAP - GWIA
>
>
> CW>-------------
> CW>I am not familiar enough with ldap to tell whether the base64 code as a
> CW>cn property is odd or not, but it is typical of the entire
> listing. Note
> CW>that this cn line always has 2 '::' (colon's) instead of just
> one - this
> CW>may be significant but I don't know.
>
> Again, this may be off the mark, but the reason I was curious about the cn
> values is that the default filter attribute in imp's ldap query is the cn
> attribute.  I don't know what you'll get querying against the kind of cn
> attribute you're showing above.
>
> I take it you get the same results when you query against surname (sn) or
> givenname, right?  What happens if you edit the default $str_search in
> ldap.search.php3, changing it from cn to sn?  (No, I haven't done this...)
>
-------
Yes, I get the same result regardless of whether I query against surname,
name, givenName, is, is(strict), contains, begins with,ends with.

if my imp/config/defaults.php3 is...
$LDAPServers['aidssc'] = new LDAPServer('aidssc',
                                           'AIDSSC',
                                           '192.168.1.2',
                                           'dc=aidssc,dc=org',
                                           'sn',
                                           'cn,mail,sn,givenname',

'is,is_strict,contains,begins,ends');

Wouldn't that signify that the surname is the default $str_search? I changed
the lone sn on the 5th line to cn but it returned the same results. FWIW,
searching Bigfoot works.

Craig