On Thu, Apr 16, 2015 at 10:39:59PM +0200, Arthur de Jong wrote:
> On Wed, 2015-04-15 at 19:07 +0200, أحمد المحمودي wrote:
> > I am experiencing the issue of login failure with cached credentials,
> > yet stopping nslcd no longer helps, rather I get this
> > in /var/log/auth.log:
> > Apr 15 18:19:42 myhostname login[13342]: pam_ldap(login:auth): error 
> > opening connection to nslcd: No such file or directory
> 
> Could you provide the contents of /etc/pam.d/common-auth?
> 
> The default configuration has
>   auth [success=1 default=ignore] pam_ldap.so minimum_uid=1000 use_first_pass
> which is supposed to ignore PAM_AUTHINFO_UNAVAIL and continue with the
> next PAM module.
---end quoted text---

  Please find /etc/pam.d/common-auth attached.

-- 
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7
#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.).  The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-6, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules.  See
# pam-auth-update(8) for details.

# here are the per-package modules (the "Primary" block)
auth    [success=4 default=ignore]      pam_unix.so nullok_secure
auth    [success=3 authinfo_unavail=ignore default=ignore]      pam_ldap.so 
minimum_uid=1000 use_first_pass
auth    [success=2 default=ignore]      pam_ccreds.so minimum_uid=1000 
action=validate use_first_pass
auth    [default=ignore]                pam_ccreds.so minimum_uid=1000 
action=update
# here's the fallback if no module succeeds
auth    requisite                       pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth    required                        pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth    optional                        pam_ccreds.so minimum_uid=1000 
action=store
# end of pam-auth-update config

Attachment: signature.asc
Description: Digital signature

Reply via email to