Hide Forgot
This bug is created as a clone of upstream ticket: https://fedorahosted.org/sssd/ticket/1137 In {{{sdap_get_tgt_recv()}}} and {{{krb5_child_done()}}} we should report errors while acquiring the TGT to syslog, not just the debug logs. This would help with triaging errors, as such common problems as clock skew would be easy to detect.
Verified on sssd-1.8.0-22.el6.x86_64. The output for the associated beaker automation script is given below: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: Verify BZ release ticket #289 :- Kerberos errors should go to syslog :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ PASS ] :: Running 'change_date' :: [ PASS ] :: Running 'sleep 5s' :: [ PASS ] :: Expecting clock skew error :: [ PASS ] :: Log message exists in syslog as expected. :: [ PASS ] :: Running 'reset_date' :: [ PASS ] :: Running 'chmod 755 /tmp/a1m2deluser.sh' :: [ PASS ] :: Running 'expect /tmp/a1m2deluser.sh' :: [ LOG ] :: Duration: 1m 42s :: [ LOG ] :: Assertions: 18 good, 0 bad :: [ PASS ] :: RESULT: Verify BZ release ticket #289 :- Kerberos errors should go to syslog
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: SSSD would log errors in Kerberos authentication only into its own debug logs Consequence: Users would have difficulty tracking down the cause of errors with authentication Fix: Errors occurred during Kerberos authentication are now sent to the syslog in addition to the debug logs. Result: Users will see failures to authenticate in a standard location, making it easier to track down the cause.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0747.html