#334 SSSD Kerberos does not renew ticket on screen lock.
Closed: Duplicate Opened by dpal.

- In the morning around 10 am authenticated to log into the machine after reboot. Was offline at that time.
- Got online and worked on the VPN. Did not authenticate using kinit.
- Left computer for couple hours in the middle of the day. The screen go locked while maintaining VPN connection. 
- Came back and unlocked the screen. Worked for some time. 
- Tried to log into wiki and got error.
- Checked the ticket. It was like this:
[dpal@dpal Desktop]$ klist
Ticket cache: FILE:/tmp/krb5cc_12785_AVi7l9
Default principal: dpal@REDHAT.COM
Valid starting     Expires            Service principal
12/31/69 19:00:00  12/31/69 19:00:00  krbtgt/REDHAT.COM@REDHAT.COM
Kerberos 4 ticket cache: /tmp/tkt12785
klist: You have no tickets cached

Pay attention to the time stamps.

Expected result: the ticket is correctly renewed and stored during screen unlock operation.


Fields changed

description:
* In the morning around 10 am authenticated to log into the machine after reboot. Was offline at that time.
* Got online and worked on the VPN. Did not authenticate using kinit.
* Left computer for couple hours in the middle of the day. The screen go locked while maintaining VPN connection.
* Came back and unlocked the screen. Worked for some time.
* Tried to log into wiki and got error.
* Checked the ticket. It was like this:
{{{
[dpal@dpal Desktop]$ klist
Ticket cache: FILE:/tmp/krb5cc_12785_AVi7l9
Default principal: dpal@REDHAT.COM

Valid starting Expires Service principal
12/31/69 19:00:00 12/31/69 19:00:00 krbtgt/REDHAT.COM@REDHAT.COM

Kerberos 4 ticket cache: /tmp/tkt12785
klist: You have no tickets cached
}}}

Pay attention to the time stamps.

'''Expected result:''' the ticket is correctly renewed and stored during screen unlock operation.

=>
* In the morning around 10 am authenticated to log into the machine after reboot. Was offline at that time.
* Got online and worked on the VPN. Did not authenticate using kinit.
* Left computer for couple hours in the middle of the day. The screen go locked while maintaining VPN connection.
* Came back and unlocked the screen. Worked for some time.
* Tried to log into wiki and got error.
* Checked the ticket. It was like this:
{{{
[dpal@dpal Desktop]$ klist
Ticket cache: FILE:/tmp/krb5cc_12785_AVi7l9
Default principal: dpal@REDHAT.COM

Valid starting Expires Service principal
12/31/69 19:00:00 12/31/69 19:00:00 krbtgt/REDHAT.COM@REDHAT.COM

Kerberos 4 ticket cache: /tmp/tkt12785
klist: You have no tickets cached
}}}

Pay attention to the time stamps.

'''Expected result:''' the ticket is correctly renewed and stored during screen unlock operation.

Fields changed

owner: somebody => sbose

Logs from my sssd folder.
logs.tar.gz

What is the build date of your rpm?

Please try to reproduce with a package build after 12/15/09 because the final patch for #321 was only committed then.

Fields changed

summary: SSSD Kerberos does not review ticket on the screen lock. => SSSD Kerberos does not renew ticket on screen lock.

manual tests have been written to cover kerberos ticket creation and update on console screen locks and logins.

testsupdated: 0 => 1

We believe that this bug was a duplicate of #321 and #344

If the problem persists with a build after Dec 18th, please reopen.

resolution: => duplicate
status: new => closed

Fields changed

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => void

Metadata Update from @dpal:
- Issue assigned to sbose
- Issue set to the milestone: void

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1376

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata