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 was initially created as a clone of Bug #1056078 +++

These patches are needed to allow gssproxy to selectively disable rcaches or implement separate rcache for separate services.

In particular these patches are critical to be able to handle upstream bug:
https://fedorahosted.org/gss-proxy/ticket/101

The relevant patches are:

preparatory:
https://github.com/krb5/krb5/commit/74ff6c4accb68bd1d6c652c55e66519720db9fc4
https://github.com/krb5/krb5/commit/ef8e19af863158e4c1abc15fc710aa8cfad38406
https://github.com/krb5/krb5/commit/9df0c4bdce6b88a01af51e4bbb9a365db00256d5

actual fix:
https://github.com/krb5/krb5/commit/7dad0bee30fbbde8cfc0eacd2d1487c198a004a1

optional additional fix:
https://github.com/krb5/krb5/commit/970304b558a360e08d8421ef92245d2df0ac5e49

optional test (depends on optional fix):
https://github.com/krb5/krb5/commit/6f8d5135334c9ddb674f9824e750872b3b0642ea


Is it possible to backport to F19 too ?

It would be really useful to have this in RHEL 7 too.

Provided the self-tests get backported, too, a manual 'make -C src/tests/gssapi' outside of the build system should exercise the new code.  Simo, is there a more easily-reproduced procedure by way of using gssproxy?

Of course, that should be 'make -C src/tests/gssapi check'.

The simplest test I know will triger this would involve configuring a Kerberos Realm, gssproxy, apache, mod_auth_kerb, and intercept a browser/curl negotiate authentication.
With cred_store=rcache:none:none it should work, and without it it should fail.

Sorry, I do not have a simpler test available atm.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.