Installing libpam-foreground or removing the reference to it in /etc/pam.d/common-session will clear up the first error. The second error probably stems from misconfiguration in /etc/ldap.conf... particularly with how PAM tries to contact your LDAP server (uri, port, ssl/tls directives).
2009/7/20 Asimananda Mohanty email@example.com
The command mentioned by you is running fine and it doesn't show any error.
That means that simple bind works fine.
*By stating "I am able to login to the server", I meant that I am able to establish an ssh session (via putty) with the server by providing user id and password. In that case, I don't really understand the error while logging in by that user id.*
Thanks for your support.
2009/7/20 Michael Ströder firstname.lastname@example.org
Asimananda Mohanty wrote:
I think the LDAP in current form should solve my purpose.
Currently I have client and server on the same machine. I have created one user in LDAP namely asimananda and I am able to login to the server by the same too.
What does "I am able to login to the server" mean exactly. Did you test with ldapwhoami -x -D <bind-DN of asimananda> -W whether simple bind works?
*PAM unable to dlopen(/lib/security/pam_foreground.so): /lib/security/pam_foreground.so: cannot open shared object file: No such file or directory PAM adding faulty module: /lib/security/pam_foreground.so pam_ldap: ldap_simple_bind Can't contact LDAP server pam_ldap: reconnecting to LDAP server... pam_ldap: ldap_simple_bind Can't contact LDAP server Successful su for asimananda by root
- pts/3 root:asimananda
pam_unix(su:session): session opened for user asimananda by root(uid=0)*
Looks like an setup error in your PAM setup. Check the ldap.conf related to the pam_ldap module. I don't know Ubuntu so I can't help here.