sssd doesn't play a role here, since it doesn't use libpam-mklocaluser..
just fix your local setup.
** Changed in: sssd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Package changed: ubuntu => sssd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914461
Title:
common-session should not create a local user when using sssd
To manage notifications about t
Smal typo in my comment above. "if you do not want to use libpam-
mkhome" should read "if you do want to use libpam-mkhome"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914461
Title:
common-sessio
This bug seem to be misclassified. If I understand it correctly, it is
a request for not using libpam-sss and libpam-mklocaluser together if
you want to use libpam-mkhome instead of libpam-mklocaluser. And while
that seem correct enough - if you do not want to use libpam-mkhome,
please do so. Bu
** Package changed: ubuntu => libpam-mklocaluser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914461
Title:
common-session should not create a local user when using sssd
To manage notific
This is the common-session entry that I think is wrong.
sessionrequired pam_python.so /usr/lib/libpam-mklocaluser/pam-
python.py
It should be something like
session required pam_mkhomedir.so skel=/etc/skel umask=077
--
You received this bug notification because you are a member of Ubun
