On Sat, Jul 28, 2012 at 4:25 PM, fosiul alam <expertalert(a)gmail.com> wrote:
Dont know how to reply on same thread.
Just click on reply & leave the subject of mail un-touched
but thank for quick reply.
its case sensitive. so I created the cert file
and i put that one into client , and i configured as documentated
and in /etc/ldap.conf
You should use pam_password clear because Your password is being hashed by
your client system before it is sent to the Directory Server. This is not
allowed since the server would have no way to enforce it's password policy
against a pre-hashed password. You need to configure /etc/ldap.conf to
send the clear text password to the LDAP server. You should use SSL/TLS to
protect the password in transit (which you already have).
and i can see it created another file in /etc/openldap/cacerts/ directory
and when i do like this
it does not find the user and i dont see any error in /var/log/message
so its like its connecting to ldap. .but it does not get any information
do i have to say Cn="Directory Manager" some where in ldap.conf file ??
thanks for your help.
but in clients , log file
Copy the my-public-ca.asc file in /etc/openldap/cacerts
# cp my-public-ca.asc /etc/openldap/cacerts
# cacertdir_rehash /etc/openldap/cacerts
This will create file like below. (Check for the soft link file ending with
[root@atolani cacerts]# ll
lrwxrwxrwx. 1 root root 16 Apr 24 11:16 2c47a1a7.0 -> my-public-ca.asc
-rw-r--r--. 1 root root 851 Apr 9 01:13 my-public-ca.asc
Now try to run ldapsearch using -ZZ (for start_tls) Make sure you give the
exact hostname which you used while creating the cert in this step.
"certutil -S -n "server-cert" -s
Something like this.
ldapsearch -x -ZZ -D "cn=Directory manager" -w password -h
If this works, Then your TLS is working. Now try to configure pam_ldap with