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.
Bug 1722842 - sssd-kcm does not store TGT with ssh login using GSSAPI
Summary: sssd-kcm does not store TGT with ssh login using GSSAPI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 8.0
Assignee: jstephen
QA Contact: Anuj Borah
URL:
Whiteboard: sync-to-jira qetodo
Depends On: 1881992
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-21 13:18 UTC by Stefan Walter
Modified: 2023-12-15 16:34 UTC (History)
12 users (show)

Fixed In Version: sssd-2.4.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:03:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
krb5.conf (484 bytes, text/plain)
2019-06-21 13:18 UTC, Stefan Walter
no flags Details
sshd_config (716 bytes, text/plain)
2019-06-21 13:18 UTC, Stefan Walter
no flags Details
ssh_config (780 bytes, text/plain)
2019-06-21 13:19 UTC, Stefan Walter
no flags Details
sssd.conf (1.14 KB, text/plain)
2019-06-21 13:23 UTC, Stefan Walter
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5333 0 None closed sssd-kcm does not store TGT with ssh login using GSSAPI 2021-02-16 13:16:03 UTC
Github SSSD sssd pull 5428 0 None closed TESTS:sssd-kcm does not store TGT with ssh login using GSSAPI 2021-02-16 13:16:03 UTC

Description Stefan Walter 2019-06-21 13:18:20 UTC
Created attachment 1583187 [details]
krb5.conf

Description of problem:

A RHEL 8.0 system set up for GSSAPI login for ssh allows to log in but does not actually store the ticket. klist shows no ticket after login. NFS4 with kerberos does not mount a home directory as a result.


Version-Release number of selected component (if applicable):

sssd-kcm-2.0.0-43.el8_0.3.x86_64
openssh-7.8p1-4.el8.x86_64
krb5-workstation-1.16.1-22.el8.x86_64


Additional info:

Running sshd in debug mode shows this:

debug1: temporarily_use_uid: 50515/103585 (e=0/0)
debug3: ssh_krb5_cc_new_unique: called
debug3: ssh_krb5_get_cctemplate: called
debug3: ssh_krb5_expand_template: called, template = KCM:
debug3: ssh_krb5_get_cctemplate: returning with ccname = KCM:
debug3: ssh_krb5_cc_new_unique: setting default ccname to KCM:
debug3: ssh_krb5_cc_new_unique: calling cc_new_unique(KCM:)
debug3: ssh_krb5_cc_new_unique: calling cc_switch()
ssh_krb5_cc_new_unique(): End of credential cache reached

which seems to indicate an error trying to store the TGT.

ssh_config, sshd_config and krb5.conf are attached.

Comment 1 Stefan Walter 2019-06-21 13:18:44 UTC
Created attachment 1583188 [details]
sshd_config

Comment 2 Stefan Walter 2019-06-21 13:19:23 UTC
Created attachment 1583189 [details]
ssh_config

Comment 3 Stefan Walter 2019-06-21 13:23:37 UTC
Created attachment 1583190 [details]
sssd.conf

Comment 4 Stefan Walter 2019-06-24 08:18:54 UTC
Update: When using 'KEYRING' as cache the ticket is correctly forwarded. sshd logs the following in this case:

...
debug1: temporarily_use_uid: 50515/103585 (e=0/0)
debug3: ssh_krb5_cc_new_unique: called
debug3: ssh_krb5_get_cctemplate: called
debug3: ssh_krb5_expand_template: called, template = KEYRING:persistent:%{uid}
debug3: ssh_krb5_get_cctemplate: returning with ccname = KEYRING:persistent:50515
debug3: ssh_krb5_cc_new_unique: setting default ccname to KEYRING:persistent:50515
debug3: ssh_krb5_cc_new_unique: calling cc_new_unique(KEYRING:persistent:50515)
debug3: ssh_krb5_cc_new_unique: calling cc_switch()
debug1: restore_uid: 0/0
...

Comment 8 kludhwan 2019-07-24 11:41:02 UTC
Hello Jakub,

Customer feedback.

Removing 'ccache_storage = memory' fixes this issue. That works for us so please close this request and the associated bug report unless RH wants to actually fix this also for the memory ccache storage.

Thanks,
Kushal

Comment 14 jstephen 2020-09-23 17:17:14 UTC
Upstream ticket:
https://github.com/SSSD/sssd/issues/5333

Comment 15 Pavel Březina 2020-09-29 12:24:29 UTC
Pushed PR: https://github.com/SSSD/sssd/pull/5313

* `master`
    * f126afc98e1e7ae1df685980dd1773e81ae10668 - KCM: Fix GSSAPI delegation for the memory back end

Comment 25 errata-xmlrpc 2021-05-18 15:03:54 UTC
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:1666


Note You need to log in before you can comment on or make changes to this bug.