From e7a24374d97e1d1c32d3e18561a20e8c5e6319ec Mon Sep 17 00:00:00 2001 From: Jakub Hrozek Date: Tue, 9 Oct 2012 19:02:22 +0200 Subject: Collect krb5 trace on high debug levels If the debug level contains SSSDBG_TRACE_ALL, then the logs would also include tracing information from libkrb5. https://fedorahosted.org/sssd/ticket/1539 --- src/util/sss_krb5.h | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'src/util/sss_krb5.h') diff --git a/src/util/sss_krb5.h b/src/util/sss_krb5.h index 15dd1e6a6..708914c6c 100644 --- a/src/util/sss_krb5.h +++ b/src/util/sss_krb5.h @@ -34,6 +34,9 @@ #include "util/util.h" +#define KRB5_CHILD_LOG_FILE "krb5_child" +#define LDAP_CHILD_LOG_FILE "ldap_child" + /* MIT Kerberos has the same hardcoded warning interval of 7 days. Due to the * fact that using the expiration time of a Kerberos password with LDAP * authentication is presumably a rare case a separate config option is not @@ -164,4 +167,8 @@ typedef krb5_ticket_times sss_krb5_ticket_times; typedef krb5_times sss_krb5_ticket_times; #endif +void +sss_child_krb5_trace_cb(krb5_context context, + const struct krb5_trace_info *info, void *data); + #endif /* __SSS_KRB5_H__ */ -- cgit