Learn more about these different git repos.
Other Git URLs
I could not find a similar ticket, please close this one if it's already been reported.
We need better handling of PAM error 4, sometimes it should be redirecting/converted to other error code, other times to provide a bit more (hopefully useful) info.
Example(s): Relating to: Server not found in Kerberos database, Received error code 1432158209
(Wed Feb 10 12:49:50 2016) [sssd[be]] [be_pam_handler_callback] (0x0100): Backend returned: (0, 4, <NULL>) [Success] (Wed Feb 10 12:49:50 2016) [sssd[be]] [be_pam_handler_callback] (0x0100): Sending result [4] (Wed Feb 10 12:49:50 2016) [sssd[be]] [be_pam_handler_callback] (0x0100): Sent result [4]
I will provide further explanation and examples in the downstream BZ since the customer wants to keep his info away from upstream trackers.
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1306707 (Red Hat Enterprise Linux 7)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1306707 1306707]
Capturing the discussion from our developer's meeting: - we'll return a special SSSD error code from the krb5_child denoting this error condition - we'll handle this special error code in the sssd_be process. That will give us an opportunity to print a more descriptive error message and hint to admin where to look at
Moving the ticket into 1.14 beta, marking as minor.
milestone: NEEDS_TRIAGE => SSSD 1.14 beta priority: major => minor
Shouldn't block the 1.14 beta release.
milestone: SSSD 1.14 beta => SSSD 1.14.0
1.14.0 should be released no later than Wednesday next week, this ticket should not block the 1.14.0 release.
milestone: SSSD 1.14.0 => SSSD 1.14.1
We need to release 1.14.1 soon, therefore moving to 1.14.2.
keywords: sssd, pam => easyfix milestone: SSSD 1.14.1 => SSSD 1.14.2
Fields changed
type: feature => defect
Moving tickets that didn't make it into the 1.14.2 release into the next point release.
milestone: SSSD 1.14.2 => SSSD 1.14.3
Petr, this might be an interesting ticket for you. See comment #2 for an idea and feel free to pick this ticket up if you agree.
cc: => pcech
patch: 0 => 1
owner: somebody => jhrozek status: new => assigned
master:
sssd-1-14:
And I think it's a usefull debug message and can be also in LTS branch
sssd-1-13:
I don't intend to add more commits, so closing.
resolution: => fixed status: assigned => closed
Metadata Update from @gagrio: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.14.3
despite what the previous comment says, here is another commit: 7410f73
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch adjusted to on (was: 1) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0)
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/3996
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.