Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionChance Callahan
2023-04-05 21:52:08 UTC
1. Proposed title of this feature request
Add option to create unique credential caches on the disk in /etc/krb5.conf
3. What is the nature and description of the request?
On VAS/QAS, their implementation of Kerberos allows unique identifiers at the end of the credential cache file:
Ticket cache: FILE:/tmp/krb5cc_4132744_aqzIRXKmQr
vs.
Ticket cache: FILE:/tmp/krb5cc_4132744
The customer would like to see similar behavior with RHEL.
4. Why does the customer need this? (List the business requirements here)
The customer has multiple programs logging into a shell account and doesn't want the ticket renewed each time, they want one persistent ticket per session.
5. How would the customer like to achieve this? (List the functional requirements here)
They would like a unique string/identifier added to the end of each credential cache file.
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
This can be tested with klist.
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No.
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
No.
9. Is the sales team involved in this request and do they have any additional input?
No.
10. List any affected packages or components.
krb5-workstation-1.15.1-37.el7_6.x86_64
11. Would the customer be able to assist in testing this functionality if implemented?
Yes.
The KEYRING credential cache type seems to already meet these requirements, especially its "KEYRING:persistent:uidnumber" configuration[1]. It provides a per-user ccache that survives user logout, and remains valid for the full lifetime of the TGT.
I think SSSD's implementation of the KCM credential cache supports this kind of behavior too. It is also capable of renewing tickets automatically.
We are not likely to implement new features for file-based credential cache types. We are privileging in-kernel or in-process credential store as they are less vulnerable to secret steeling.
[1] https://web.mit.edu/kerberos/krb5-1.20/doc/basic/ccache_def.html#ccache-types
Comment 5RHEL Program Management
2023-09-18 22:36:37 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6RHEL Program Management
2023-09-18 22:41:37 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.