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.
Created attachment 988587[details]
goa daemon log
Description of problem:
Kerberos ticket auto-renewal not working
Version-Release number of selected component (if applicable):
gnome-online-accounts-3.8.5-14.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. Login using a smartcard that has a kerberos user that has a ticket lifetime of 32 hours
2. Create a keyring password when prompted for
3. The following is what my /etc/krb5.conf looks like
[libdefaults]
dns_lookup_realm = false
ticket_lifetime = 32m
renew_lifetime = 72h
forwardable = true
rdns = false
default_realm = EXAMPLE.COM
default_ccache_name = KEYRING:persistent:%{uid}
.
.
.
[appdefaults]
pam = {
debug = true
ticket_lifetime = 32m
renew_lifetime = 72h
forwardable = true
krb4_convert = false
}
The following is what my kdc.conf in the KDC server looks like
[realms]
EXAMPLE.COM = {
#master_key_type = aes256-cts
acl_file = /var/kerberos/krb5kdc/kadm5.acl
dict_file = /usr/share/dict/words
admin_keytab = /var/kerberos/krb5kdc/kadm5.keytab
supported_enctypes = aes256-cts:normal aes128-cts:normal des3-hmac-sha1:normal arcfour-hmac:normal camellia256-cts:normal camellia128-cts:normal des-hmac-sha1:normal des-cbc-md5:normal des-cbc-crc:normal
pkinit_anchors = FILE:/var/kerberos/krb5kdc/kdc-ca.pem
pkinit_identity = PKCS12:/var/kerberos/krb5kdc/kdc.p12
pkinit_allow_upn = on
pkinit_eku_checking = scLogin
max_renewable_life = 7d
}
Also attaching the goa daemon log
Actual results:
Kerberos ticket should be automatically renewed
Expected results:
Kerberos ticket is not automatically renewed
Additional info:
(In reply to Roshni from comment #0)
> Steps to Reproduce:
> 1. Login using a smartcard that has a kerberos user that has a ticket
> lifetime of 32 hours
Let's ignore the smartcard bit for the time being.
This has been a long-standing issue with gnome-online-accounts. It would not try to refresh the ticket across session restarts, or during network changes. This has now been fixed upstream and I will backport it for RHEL 7.2.
If there are, indeed, any smartcard specific issues, we can use a separate bug.
One crude way of testing it is:
(i) Disconnect from the network that has the KDC.
(ii) Use kdestroy to delete the ticket.
(iiia) Restart goa-daemon (/usr/libexec/goa-daemon --replace)
(iiib) Rejoin the network that has the KDC
Using gnome-online-accounts-3.14.4-2.el7 I still see the issue reported in the bug. Seeing the issue when logged in using smartcard with a kerberos user and also when logged in using kerberos user password.
Ray, could you have a look at this ? Debarshi is out next week, unfortunately.
Comment 9Ray Strode [halfline]
2015-09-22 18:53:39 UTC
I looked into this a bit today. There were a few issues:
1) we were only honoring renewal requests right at start up, but of a strangely missing if() statement in the code
2) we were failing to keep a constant renewal time for kernel keyring based credential caches
3) crasher fix for a corner case i noticed that maybe only happens if you have a break point in gdb in the right place for an extended period of time.
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, 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://rhn.redhat.com/errata/RHBA-2015-2157.html
Created attachment 988587 [details] goa daemon log Description of problem: Kerberos ticket auto-renewal not working Version-Release number of selected component (if applicable): gnome-online-accounts-3.8.5-14.el7.x86_64 How reproducible: always Steps to Reproduce: 1. Login using a smartcard that has a kerberos user that has a ticket lifetime of 32 hours 2. Create a keyring password when prompted for 3. The following is what my /etc/krb5.conf looks like [libdefaults] dns_lookup_realm = false ticket_lifetime = 32m renew_lifetime = 72h forwardable = true rdns = false default_realm = EXAMPLE.COM default_ccache_name = KEYRING:persistent:%{uid} . . . [appdefaults] pam = { debug = true ticket_lifetime = 32m renew_lifetime = 72h forwardable = true krb4_convert = false } The following is what my kdc.conf in the KDC server looks like [realms] EXAMPLE.COM = { #master_key_type = aes256-cts acl_file = /var/kerberos/krb5kdc/kadm5.acl dict_file = /usr/share/dict/words admin_keytab = /var/kerberos/krb5kdc/kadm5.keytab supported_enctypes = aes256-cts:normal aes128-cts:normal des3-hmac-sha1:normal arcfour-hmac:normal camellia256-cts:normal camellia128-cts:normal des-hmac-sha1:normal des-cbc-md5:normal des-cbc-crc:normal pkinit_anchors = FILE:/var/kerberos/krb5kdc/kdc-ca.pem pkinit_identity = PKCS12:/var/kerberos/krb5kdc/kdc.p12 pkinit_allow_upn = on pkinit_eku_checking = scLogin max_renewable_life = 7d } Also attaching the goa daemon log Actual results: Kerberos ticket should be automatically renewed Expected results: Kerberos ticket is not automatically renewed Additional info: