Bug 241930 - authentication to server from evolution stops working after a time
authentication to server from evolution stops working after a time
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: openldap (Show other bugs)
6
All Linux
low Severity medium
: ---
: ---
Assigned To: Jan Safranek
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-31 15:08 EDT by Thomas J. Baker
Modified: 2008-01-29 06:21 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-29 06:21:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Thomas J. Baker 2007-05-31 15:08:07 EDT
After the latest update to openldap-servers, my evolution client periodically
starts having authentication problems to my ldap server. Evolution prompts for
the password, indicating an authentication failure because it's already storing
the password, and repeated attempts to reauthenticate don't work. If I stop and
start the ldap server, I can then authenticate correctly. 

I'm using an up to date FC6 x86_64 setup with openldap-servers-2.3.30-2.fc6.
Comment 1 Jan Safranek 2007-08-07 05:00:26 EDT
sorry for long time to respond... but I am not able to reproduce the bug in my
environment. Could you please provide more information?

- which openldap-servers did you use before it got broken?
- which version of evolution are you using?
- please attach your /etc/openldap/slapd.conf and ldif dump of your database
(feel free to use dummy email addresses/user names, but please check, that the
communication with evolution is still broken)
- if you have Fedora-7 installed somewhere with openldap-servers and evolution,
does it have the same problem?
- do you use TLS or SSL communication between evolution and openldap?
Comment 2 Jan Safranek 2008-01-29 06:21:24 EST
I cannot reproduce the bug and the reporter did not provide requested
information. Please reopen the bug if the bug persists and you are able to
provide the info I need.

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