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.
DescriptionAlexey Tikhonov
2022-05-23 09:03:48 UTC
This bug was initially created as a copy of Bug #2088817
I am copying this bug because: to track fix for RHEL9
Description of problem:
I've recently upgraded AlmaLinux from 8.5 to 8.6.
I am using pam_sss_gss together with sudo.
This setup ceased to work under certain circumstances:
- it does NOT work when logged in using sss with gssapi-keyex authentication
- it works when logged in on Linux console (both text and sddm work).
Version-Release number of selected component (if applicable):
sssd-client-2.6.2-4.el8_6.x86_64
How reproducible:
Always, as described above.
Steps to Reproduce:
1. Log in using ssh and GSSAPI authentication to IPA client system.
2. Add 'auth sufficient pam_sss_gss.so' as the first line to /etc/pam.d/sudo and configure sssd.conf for the above.
3. Invoke 'sudo -l'. It asks for password while it should succeed with sss gss authentication.
4. When debug is enabled the following is printed:
pam_sss_gss: sss_cli_getenv() call failed [2]: No such file or directory
Actual results:
SSSD GSS authentication fails. sudo prompts for password.
Expected results:
SSSD GSS authentication succeeds. No password prompt.
Additional info:
This is caused by introduction of 'sss_cli_getenv' function in pam_sss_gss.c file and mishandling the NULL result from 'getenv' function. NULL is perfectly valid and SHOULD NOT result in error (ENOENT) returned by this function, especially that this case is properly handled by previous version of the module where default cache is picked (from sssd-client-2.5.2).
Please note the comment above call to 'sss_cli_getenv':
/* Get non-default ccache if specified, may be NULL. */
clearly indicates that the requested environment variable is OPTIONAL. Please handle it as such.
The same issue exists on Fedora 35.
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-2022:8325