Fields changed

version: 1.3.1 => 1.2.4

May be deferred.

milestone: NEEDS_TRIAGE => SSSD 1.5.0

Fields changed

priority: major => critical

Fields changed

owner: somebody => sgallagh

There's no bug here. SSSD is behaving exactly as expected.

The PAM stack has:

session     optional      pam_keyinit.so revoke
session     required      pam_limits.so
session     [success=1 default=ignore] pam_succeed_if.so service in crond quiet
use_uid
session     required      pam_unix.so
session     optional      pam_sss.so
session     optional      pam_krb5.so
session     optional      pam_ldap.so

Note that pam_sss.so is listed as "optional". This means that even if SSSD
succeeds, it will still check to see if pam_sss.so has anything to do.

It enters the pam_sss.so processing and we discover that it's not a user we
handle, so we report that in the debug log and return.

resolution: => invalid
status: new => closed

Fields changed

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=641908 641908]

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1690

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.