RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/3106

The ldap_child helper process creates a temporary file and then acquires credentials, which is a synchronous operation. If that takes more than a configured timeout, the parent (sssd_be) kills the child process with SIGTERM. But if the child process is killed, we don't remove the temporary file. We need to fix that..

master:
    864cdac4c7fbe768d768da5e01b7518eb02836d9
    b9a0959c274367dcf69bba6b0a942a1682c74f73
    4313147ab4214037900cbb3ced8a03e492bff02c 
sssd-1-13:
    41afbb6b86d592be2d0f831dbea4f4d92b73cdb5
    09403b66fa73d294f38ddd4afa4d32eaf8d92087
    96e135a1b42c565c257e525c1eb04751058e6836

Verified Sanity only on SSSD Version: sssd-1.15.2-37.el7.x86_64

Following automated test suites cover ldap_child & ldap_sasl_authid:

LDAP-KRB tests : https://beaker.engineering.redhat.com/jobs/1883216
AD provider ldap-krb tests: https://beaker.engineering.redhat.com/jobs/1883386

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.

https://access.redhat.com/errata/RHEA-2017:2294