After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 267541 - LDAP password not remembered
LDAP password not remembered
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Contacts
2.0.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 252374 261246 270156 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-10-05 09:16 UTC by David O
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David O 2004-10-05 09:16:31 UTC
Description of Problem:
I have LDAP configured for contacts. I authenticate to the server, and
click 'Remember this password'. This works. However, a short time later it
asks me to authenticate again. This time, my password gets rejected every
time, no matter if I have checked 'Remember this password' or not, and all
I can do is cancel.

If I start up evolution fresh, it works again, for about half an hour, then
the problem re-occurs.
Comment 1 Ramesh Dharan 2004-10-21 18:37:16 UTC
I see the exact same behavior. This is with evolution 2.0.2-3 from
debian unstable, talking to a Microsoft Exchange Active Directory LDAP
server. 

I don't know how to turn on LDAP logging or debugging but if someone
can tell me how I can give it a shot and perhaps add some more useful
verbose output here...
Comment 2 David O 2004-10-22 13:24:19 UTC
I am also using Active Directory LDAP if that's significant.
Comment 3 Gerardo Marin 2004-10-26 19:39:49 UTC
*** bug 261246 has been marked as a duplicate of this bug. ***
Comment 4 Sivaiah 2004-11-02 19:51:55 UTC

*** This bug has been marked as a duplicate of http://bugzilla.ximian.com/show_bug.cgi?id=68656 ***
Comment 5 Sivaiah 2004-11-02 19:52:51 UTC
oops wrong duplicate 
Comment 6 Sivaiah 2004-11-04 04:14:57 UTC
Run evolution data server in a terminal and attached the debug output
you get there when this error happens, my guess is that ldap
connections timing out when there are no operations for long time and
evo is not reconnecting. lokk for idle time out settings in your
/etc/ldap.conf or similar conf files 
Comment 7 David O 2004-11-04 14:00:07 UTC
Every time the auth fails, I simply get a line such as:

simple auth as <username>

Where I've replaced username with the name I'm authenticating to LDAP
with. Then I just get the LDAP login box again.

I also notice that the first time the authentciation works, I get the
following warning:

(evolution-data-server:2118): libebookbackend-WARNING **: subschema
read returned nothing before successful auth
simple auth as <username>

I have no timeouts defined in /etc/ldap.conf

Is there anything else I can do to get some more detail on where it's
failing?
Comment 8 Sivaiah 2004-12-06 17:17:26 UTC
*** bug 270156 has been marked as a duplicate of this bug. ***
Comment 9 madcap 2004-12-06 17:31:53 UTC
As stated in bug 270156, this happens against M$ Exchange 2000's LDAP
server too.
Comment 10 madcap 2004-12-06 17:35:30 UTC
I'm trying to run evolution-data-server in a terminal as suggested,
but getting errors. I've killed the existing process, and running
/usr/libexec/evolution-data-server-1.0 gets me this:

evolution-data-server-Message: Starting server
libedata-book-Message: Error registering the PAS factory: already active

evolution-data-server-ERROR **: server.c:356: could not initialize
Server service "BOOKS"; terminating
aborting...
Aborted
Comment 11 Sivaiah 2004-12-21 09:01:25 UTC
that error indicates that evolution-data-server is already running ,
please do evolution --force-shutdown and then start data server 
Comment 12 Sivaiah 2005-02-10 15:49:44 UTC
it is not telated to password remembering. ldap simple bind fails with
LDAP_SERVER_DOWN when there is no operation with the ldap handle for
some time. Sent a patch 
Comment 13 Sivaiah 2005-02-14 20:17:58 UTC
fixed
Comment 14 Sivaiah 2005-03-28 19:46:12 UTC
*** bug 252374 has been marked as a duplicate of this bug. ***