From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: With FC1, I can configure with 'authconfig' (Cache, LDAP, TLS) and authentication works. With FC2 test3 the ldap.conf looks good, but I fail to authenticate. /var/log/security says: "pam_ldap: ldap_starttls_s: Connect error" Version-Release number of selected component (if applicable): openldap 2.1.29-1 How reproducible: Always Steps to Reproduce: 1. Install FC2 test3 2. Authconfig (Cache, LDAP, LDAP Authentication, TLS, <server>, <dn>) 3. Actual Results: nscd gets restarted, can't login Expected Results: should be able to log in (works with FC1) Additional info:
See bug 112262 The work-around on Fedora Core 2 release is to disable TLS in Authconfig, and use kdm instead of gdm (which requires TLS for some reason).
I don't have this problem in FC2t3 But I do have this problem in Fc2. I'm thinking there seem to be a packages related to this have not been install.
From the Mailling list Adding /etc/ldap.conf tls_checkpeer no Is the Solution. Bug can close.
The documentation in ldap.conf says that tls_checkpeer no is the default. I'm a newbie, can someone tell me how this info will get back to the ldap folks?
This has been reported again as new bug # 123877. To Nalin, or whoever packaged this: Please, please, please change the comments in the default configuration file if you change the source/build options! I wasted huge amounts of time because the comments still said that "tls_checkpeer no" was the default.
Just been bitten by this under FC3. Could the ldap.conf comment be changed please? :-)
This also affects RHEL 4.
*** This bug has been marked as a duplicate of 123877 ***