281389 - Support for custom LDAP filters is currently broken and/or non-documented.

Status: RESOLVED DUPLICATE of bug 119291

(Directory Graveyard :: LDAP Tools, defect)

Description

[Chris Ebenezer]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

Communicator had a set of ldap preferences that allowed filtering of directory 
lookups, on a search by search basis and on an automatic basis as the user 
typed a name into the address field.

For instance:

user_pref("ldap_2.servers.Exchange.autoComplete.attributes", "cn <mail>");
user_pref("ldap_2.servers.Exchange.autoComplete.enabled", true);
user_pref("ldap_2.servers.Exchange.autoComplete.filter", "(&(|(givenName=%1*)(sn
=%1*)(cn=%1*)(LDAPcn=%1*))(|(givenName=%2*)(sn=%2*)(cn=%2*)(LDAPcn=%2*)))");

user_pref("ldap_2.servers.Exchange.filter1.string", "(|(sn=%s*)(givenName=%s*)(c
n=%s*)(LDAPcn=%s*)(department=%s*))");

This was not accessible from the UI but was documented in the Netscape 
documentation as values that could be set up on a per directory basis in the 
prefs file.

There are a number of similiar attributes in Thunderbird, just browsing through 
the code. filter1 does exist, as does the following:

user_pref("ldap_2.server.a.autoComplete.filterTemplate", .. )
and some others like repeatFilterForWords.  The LDAP filter also now uses the 
openldap search specification format.

The values that are accepted to customise this field need to be documented 
somewhere, even if it's just a textfile contain currently valid values.  If the 
mechanism is broken - as it seems to be from experimentation - then it should 
be added to the list of things to fix.

It is unclear from the code whether this is either being worked on or has been 
left for now.

Reproducible: Always

Comment 1

[Mark Smith [:mcs]]

Last I knew, this work is not done yet.  Please see bug # 119291.

*** This bug has been marked as a duplicate of 119291 ***