Open
Bug 1140818
Opened 10 years ago
Updated 2 years ago
Address Book stopped asking for LDAP password(s)
Categories
(Thunderbird :: Address Book, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: gfedorov, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/40.0.2214.111 Chrome/40.0.2214.111 Safari/537.36
Steps to reproduce:
Note: I had this working before Thunderbird 31.5.0.
-- verify an LDAP server connection with ldapsearch ( servers lives and responds to the queries ) ;
-- set an LDAP directory server ( e.g. Preferences->Composition->Addressing->Edit Directories->Add ), switch off SSL for the sake of debugging ;
-- save it, restart thunderbird just in case, make sure it's all there.
-- go back to the same dialog, choose Edit->Offline->Download Now .
Actual results:
nothing.
most importantly, there was no password prompt for the binding part, as it was yesterday before the update. ( Yes there were saved passwords, but I have deleted them for testing, so ideally it should now ask me for a password every time. )
the ldap log gives me these two lines:
===
2015-03-08 06:47:59.638217 UTC - -809519232[7f14ce817580]: unbinding
2015-03-08 06:47:59.638287 UTC - -809519232[7f14ce817580]: unbound
===
( I set
NSPR_LOG_MODULES="ldap:5,timestamp"
, and then after an attempt to get an offline copy of an address book I get no password prompt with "Replication failed" in the GUI and these two lines in the log:
===
2015-03-08 06:47:59.638217 UTC - -809519232[7f14ce817580]: unbinding
2015-03-08 06:47:59.638287 UTC - -809519232[7f14ce817580]: unbound
===
If I'm trying to look up a name on any ldap server ( yes we have several ), I get "no matches found" and no messages in the log entirely.
Needless to say, the ldapsearch utility works fine. )
Expected results:
Do we have ( bug #833971 ) been fixed too well ?
-- the log should be much more informative, logging all operations at levels 4 and 5, and at least the errors at level 2 ;
-- but most importantly, there should be a password prompt as it was before.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•