How to configure qpopper to authenticate against LDAP server

Hi,

This is a re-post of my previous question:

I have directory server 6.0 set up on Solaris 9 system. Also, I have set up Solaris 9 system native LDAP client. The qpopper daemon is running on that client. I have re-compiled the qpopper to use PAM authentication, then 'kill -HUP' inetd. But when I try to connect to qpopper with PAM authentication, I got an error:

-ERR [AUTH] PAM authentication failed for user "nsr": No account present for user (13)

I do have user's account and I am able to retrieve the user's account information by 'ldaplist -l passwd nsr'. I guess it is related pam configuration problem, but I don't know how to configure pam for qpopper. The information provided by qpopper manual is listed below:

#%PAM-1.0

auth required /lib/security/pam_pwdb.so shadow

account required /lib/security/pam_pwdb.so

password required /lib/security/pam_cracklib.so

password required /lib/security/pam_pwdb.so nullok

use_authtok md5 shadow

session required /lib/security/pam_pwdb.so

Obviously, the example configuration is for Linux. So how I can configure Solaris pam.conf to have qpopper authenticate through pam?

My current pam.conf is listed here also:

login auth requisite pam_authtok_get.so.1

login auth required pam_dhkeys.so.1

login auth required pam_dial_auth.so.1

login auth binding pam_unix_auth.so.1 server_policy

login auth required pam_ldap.so.1

rlogin auth sufficient pam_rhosts_auth.so.1

rlogin auth requisite pam_authtok_get.so.1

rlogin auth required pam_dhkeys.so.1

rlogin auth binding pam_unix_auth.so.1 server_policy

rlogin auth required pam_ldap.so.1

rsh auth sufficient pam_rhosts_auth.so.1

rsh auth binding pam_unix_auth.so.1 server_policy

rsh auth required pam_ldap.so.1

ppp auth requisite pam_authtok_get.so.1

ppp auth required pam_dhkeys.so.1

ppp auth required pam_dial_auth.so.1

ppp auth binding pam_unix_auth.so.1 server_policy

ppp auth required pam_ldap.so.1

other auth requisite pam_authtok_get.so.1

other auth required pam_dhkeys.so.1

other auth binding pam_unix_auth.so.1 server_policy

other auth required pam_ldap.so.1

passwd auth binding pam_passwd_auth.so.1 server_policy

passwd auth required pam_ldap.so.1

cron account required pam_unix_account.so.1

other account requisite pam_roles.so.1

other account binding pam_unix_account.so.1 server_policy

other account required pam_ldap.so.1

other session required pam_unix_session.so.1

other password required pam_dhkeys.so.1

other password requisite pam_authtok_get.so.1

other password requisite pam_authtok_check.so.1

other password required pam_authtok_store.so.1 server_policy

Thanks,

--xinhuan

[2885 byte] By [xhza] at [2007-11-27 10:31:28]
# 1

This is a well-known problem:

http://blogs.sun.com/raja/entry/application_popper_mis_behaving_when

s.ruta at 2007-7-28 18:09:51 > top of Java-index,Web & Directory Servers,Directory Servers...