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.
Description of problem:
Machine is joined to AD domain using realmd tool so hence /etc/krb5.keytab is populated.
I login to the machine using my AD credentials (i.e. using Kerberos), but when 'klist' command shows my personal Kerberos cache only contains machine credentials:
[victim@skynet19 gssproxy]$ klist -A
Ticket cache: FILE:/tmp/krb5cc_1099_XW1psVw
Default principal: SKYNET19$@MYDOMAIN.COM
Valid starting Expires Service principal
31/12/69 19:00:00 31/12/69 19:00:00 Encrypted/Credentials/v1@X-GSSPROXY:
Actual results:
User Kerberos cache populated with machine principals
Expected results:
User Kerberos cache contains user Kerberos principals
Additional info:
You have changed the default ccache type to FILE. FILE has a number of limitations, one of which you are encountering here (that there can only be one principal; that is, the cache is not a collection type.) You would get similar behavior out of FILE if you were to kinit as one user, then kinit a second. (i.e., you would see only the second user's TGT.)
We recommend KEYRING or KCM be used for credential caches where possible because they do not have this issue. In cases where files on disk are needed for some reason, DIR can provide this while still being a collection type.
You can find more information about this in Kerberos documentation on your machine, or in the online version of the docs https://web.mit.edu/kerberos/krb5-latest/doc/basic/ccache_def.html#collections-of-caches
Right, I did not spot the FILE ccache. So it must have been the Nomachine (www.nomachine.com) bug then - looks like they ignore /etc/krb5.conf.
BTW I still see this behavior using kernel keyring, but it only happens with root account:
1. I login to machine as root (local account)
2. kinit <some_user>
3. after some time "klist -A" also displays the machine principal (SKYNET19$ in this case)
But I am not sure if it is a bug or feature. For sure it only happens if gssproxy service is running.
Can you clarify?