Bug 1496869

Summary:	sssd-kcm does not refresh tickets
Product:	[Fedora] Fedora	Reporter:	Patrick Uiterwijk <puiterwijk>
Component:	sssd	Assignee:	Jakub Hrozek <jhrozek>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	abokovoy, amessina, asn, fidencio, jhrozek, lslebodn, pbrezina, rharwood, sbose, sgallagh, ssorce
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1627112 (view as bug list)		Environment:
Last Closed:	2018-04-11 15:31:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1627112

Description Patrick Uiterwijk 2017-09-28 16:23:46 UTC

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:

Comment 1 Jakub Hrozek 2017-09-28 18:09:55 UTC

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.

Comment 2 Patrick Uiterwijk 2017-09-28 19:50:17 UTC

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.

Comment 3 Jakub Hrozek 2017-10-05 15:06:54 UTC

Upstream ticket:
https://pagure.io/SSSD/sssd/issue/1723

Comment 4 Fabiano Fidêncio 2018-04-11 15:31:56 UTC

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.