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.

Description of problem:
Based on the discussion in bug #1645291, it turned out that the cleanup procedure for the kerberos tickets created during GSSAPI Credential forwarding or Kerberos authentication are attempted to be cleaned with root context. This works fine with all the caches, but not with the KCM:, which is the new default.

Version-Release number of selected component (if applicable):
*

How reproducible:
100%

Steps to Reproduce:
1. Run the test /CoreOS/openssh/Sanity/gssapi-ccname
2. Observe some failures with KCM: 

Actual results:
credential cache when the credential cleanup was not performed as expected with KCM 

Expected results:
The credentials are properly cleaned up (by switching to the user that has acquired them)

From the code, the cleanup procedure of the GSSAPIDelegateCredentials is called twice, once as a root from the privileged process and once as a user from the user process, which is still not correct but rules out the issue is caused by calling the cleanup from different user.

Additionally, it looks like the krb5_cc_resolve() is called with empty name argument, which is something I am wondering why it could work with other credential cache types. It looks like an issue of the test.

The problem here is that the cleanup procedure of GSSAPIDelegateCredentials is getting the NULL name which makes it fail and prevents the cleanup in any case. It is caused by the recent modifications of OpenSSH to not set the environment variables KRB5CCNAME if the default is used.

This is minor issue, which should be fixed in RHEL 8.1 and it should be documented as a know issue.

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/RHSA-2019:3702