Open Bug 1800321 Opened 2 years ago Updated 2 years ago

Recipient auto-complete from LDAP addressbook fails to ignore LDAPv3 search continuations (default for MS Active Directory), but works in main AB and TB < 102

Categories

(MailNews Core :: LDAP Integration, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: bug-reports, Unassigned)

Details

Steps to reproduce:

Compose a new e-mail and type parts of a name or address in the To: field.

Actual results:

Only one address found in the LDAP server is listed. But the OpenLDAP definitely returned multiple search results.

Side note: Querying the LDAP server in the addressbook component works as expected.

Expected results:

Present a pop-up list with all matching addresses to let the user choose the right one.

Further analysis showed that LDAP-based auto-complete is confused by LDAPv3 search continuations returned by the OpenLDAP server (referral entries). Removing this referral entries makes it work as expected.

Note that MS Active Directory by default returns LDAPv3 search continuations when using top domain level DN as search root no matter how you set LDAP filters.

Also note that this used to work for me with older Thunderbird versions. So it's likely a regression.

Severity: -- → S3
Component: Untriaged → Message Compose Window
Summary: LDAP-based addessbook auto-complete does not properly ignore LDAPv3 search continuations → Recipient auto-complete from LDAP addressbook fails to ignore LDAPv3 search continuations (default for MS Active Directory), but works in main AB and TB < 102

Which version worked?

Component: Message Compose Window → LDAP Integration
Product: Thunderbird → MailNews Core

(In reply to Magnus Melin [:mkmelin] from comment #2)

Which version worked?

Probably something before 100. Sorry, I don't remember exactly, because it took a while until I found time to examine this more closely.

You need to log in before you can comment on or make changes to this bug.