search for: pam_nss

Displaying 5 results from an estimated 5 matches for "pam_nss".

2010 Feb 03
1
Winbind Auth - prevent some users from logging on
Hey folks, New to the list - and I hope this isn't a dumb question. I am in the process of revamping the way we authenticate to our Linux servers. Moving away from pam_ldap and pam_nss, in favor of winbind and pam_nss. The reason for this is that I feel winbindd does a better job of failing over from a unavailable authentication server than pam_ldap. In any case - I have it all working well on CentOS 5.4, but my only delimma is how to prevent unwanted users from logging onto se...
2003 Dec 22
2
OpenSSH + PADL pam_ldap.so + password aging
First, my config: Solaris 8 PADL pam_ldap v165 and pam_nss v211 OpenSSH 3.7.1.p2 All compiled with gcc 2.95.3 that ships with the Sun companion CD LDAP PAM authentication is working well with OpenSSH, privsep is disabled, challenge-response authentication is enabled. I would like to turn on password aging, which seems to be well supported by pam_ldap. L...
2007 Aug 06
1
Stability issues with Dovecot imap-login in Centos 5?
I wonder if other people are seeing stability issues with Dovecot and imap-login against LDAP? I've changed from pam_nss to ldap without nss in Dovecot to see if that helps the issue. I realise Dovecot is version 1.0 in Centos 5, would it be more advisable to switch to Cyrus? I'm using mbox mail spool files would that work with Cyrus? Chris -------------- next part -------------- An HTML attachment was scrubbed....
2003 Oct 26
1
Samba PDC+LDAP
I am installing Samba 3 with ldapsam and Unix accounts in ldap (pam_ldap/pam_nss), what is the best document to use for that -- Taymour A El Erian System Division Manager CNA, MCSE, CCNA, LPIC T.E. Data E-mail: taymour.elerian@tedata.net Web: www.tedata.net Tel: +(202)-4166600 Ext: 1101
2008 Oct 16
5
virutal resources and ssh_authorized_key
Hello! I''ve got question - how to use ssh_autorized_key as a virtual resource? I''ve got bunch of users and ssh_authorized_key virtual resources, but only users gets to the target system - ssh keys not... I write something like: class admins { @user { "username": ... } @ssh_authorized_key { "username": ensure => present, key => "...",