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.
.SSSD KCM now supports the auto-renewal of ticket granting tickets
With this enhancement, you can now configure the System Security Services Daemon (SSSD) Kerberos Cache Manager (KCM) service to auto-renew ticket granting tickets (TGTs) stored in the KCM credential cache on an Identity Management (IdM) server. Renewals are only attempted when half of the ticket lifetime has been reached. To use auto-renewal, the key distribution center (KDC) on the IdM server must be configured to support renewable Kerberos tickets.
You can enable TGT auto-renewal by modifying the [kcm] section of the `/etc/sssd/sssd.conf` file. For example, you can configure SSSD to check for renewable KCM-stored TGTs every 60 minutes and attempt auto-renewal if half of the ticket lifetime has been reached by adding the following options to the file:
----
[kcm]
tgt_renewal = true
krb5_renew_interval = 60m
----
Alternatively, you can configure SSSD to inherit `krb5` options for renewals from an existing domain:
----
[kcm]
tgt_renewal = true
tgt_renewal_inherit = domain-name
----
For more information, see the `Renewals` section of the `sssd-kcm` man page.
DescriptionStriker Leggette
2018-09-10 13:19:58 UTC
+++ This bug was initially created as a clone of Bug #1496869 +++
Description of problem:
After having switched to sssd-kcm and KCM: ccaches, sssd-kcm does not automatically refresh tickets.
Version-Release number of selected component (if applicable):
sssd-1.15.3-3.fc26.x86_64
sssd-kcm-1.15.3-3.fc26.x86_64
How reproducible:
Consistent
Steps to Reproduce:
1. In krb5.conf, set ticket_lifetime=5m and renew_lifetime=7d
2. Get a ticket
3. After 5 minutes, do a klist or use the ticket
Actual results:
The ticket has expired and using it returns errors.
Expected results:
The ticket got auto-renewed and using the ticket results in correct authenticators being produced.
Additional info:
--- Additional comment from Jakub Hrozek on 2017-09-28 14:09:55 EDT ---
Sorry, but this is not implemented yet. I hope to get the renewals implemented quite soon, not before F-27 GA, but before F-27. However, currently it doesn't work this way.
I guess the design page made it sound like the functionality is already there?
In general yes, this is of the reasons we went along with KCM by default..because currently either you log with SSSD and then it takes care of the renewals or you kinit and then you must call kinit -R to renew the ticket -- but since SSSD can only renew tickets it knows about, it wouldn't renew tickets acquired through kinit. If KCM renewed all the tickets, this problem would go away.
--- Additional comment from Patrick Uiterwijk on 2017-09-28 15:50:17 EDT ---
Ah, okay. I was following the https://fedoraproject.org/wiki/Changes/KerberosKCMCache#How_To_Test instructions: "If the Kerberos ticket that was acquired is renewable, SSSD would renew the ticket automatically.".
Maybe it would be good to update the testing instructions then.
--- Additional comment from Jakub Hrozek on 2017-10-05 11:06:54 EDT ---
Upstream ticket:
https://pagure.io/SSSD/sssd/issue/1723
--- Additional comment from Fabiano Fidêncio on 2018-04-11 11:31:56 EDT ---
As this issue is an RFE already being tracked on our pagure, I'd like to close it here.
Please, if, for some reason, you need this bug tracked on rhbz, feel free to re-open it.
I do hope this gets addressed in RHEL8 since it makes sssd-kcm rather useless.
It doesn't help at all that cifs-utils no longer looks for FILE:/tmp/krb5cc_$uid_XXXXXXXXXX - the default cache in absence of sssd-kcm - when authenticating my samba mounts from autofs.
Only FILE:/tmp/krb5cc_$uid works anymore.
(In reply to bugreports2005 from comment #42)
> I do hope this gets addressed in RHEL8 since it makes sssd-kcm rather
> useless.
> It doesn't help at all that cifs-utils no longer looks for
> FILE:/tmp/krb5cc_$uid_XXXXXXXXXX - the default cache in absence of sssd-kcm
> - when authenticating my samba mounts from autofs.
> Only FILE:/tmp/krb5cc_$uid works anymore.
Not sure I understand this message correctly, but JFYI this RFE is preliminary planned for a release in RHEL 8.5 and 9.0-beta.
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 (sssd bug fix and enhancement update), 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/RHBA-2021:4435