[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#634829: libpam-mklocaluser: login fails when used in conjunction with sssd



Package: libpam-mklocaluser
Version: 0.6
Severity: important


I am using sssd to authenticate against a Microsoft AD server. The pam configuration
was created using pam-auth-update, i.e. it is completely system generated.

When authenticating at the initial gdm login prompt, the login fails, and the logs show
the following:

Jul 20 11:22:49 it-000050 gdm[1765]: pam_sss(gdm:auth): User info message: Authenticated with cached credentials.
Jul 20 11:22:49 it-000050 gdm[1765]: pam_sss(gdm:auth): authentication success; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=wszachau
Jul 20 11:22:49 it-000050 gdm[1765]: pam_unix(gdm:session): session opened for user wszachau by (uid=0)
Jul 20 11:22:49 it-000050 pam_mklocaluser[1765]: Unexpected exception, should never happen: [Errno 10] No child processes
Jul 20 11:22:49 it-000050 pam_mklocaluser[1765]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :0
Jul 20 11:22:49 it-000050 pam_mklocaluser[1765]: WARNING: Couldn't open session for wszachau 

At this point, nscd is not running, but nslcd is running. 
If any additional information is required, please ask, and I shall provide.


-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libpam-mklocaluser depends on:
ii  libpam-python           1.0.0-2          Enables PAM modules to be written 
ii  python                  2.6.6-3+squeeze6 interactive high-level object-orie
ii  python-support          1.0.10           automated rebuilding support for P

libpam-mklocaluser recommends no packages.

Versions of packages libpam-mklocaluser suggests:
ii  libpam-sss              1.2.1-4+squeeze1 Pam module for the System Security

-- no debconf information



Reply to: