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:
Logging in with smart card pam_sss uses the fully qualified username (i.e 'username') and puts this on the pam stack. Other modules and calling applications will then use this which can have weird side effects. For example GDM uses this to set environment variables $USER, $USERNAME and $LOGNAME. These are common environment variables used by a range of applications, and having the username in fully qualified format may cause problems (applications may not expect that type of username format).
Version-Release number of selected component (if applicable):
sssd-2.0.0-43.el8_0.3.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Log in with smart card using pam_sss
2.
3.
Actual results:
pam_sss puts fully qualified name on pam stack
Expected results:
pam_sss should set the short user name
Additional info:
sssd_pam debug:
https://pastebin.com/raw/dQeLCNsF
An example of an application seemingly having problems using the fully qualified name is AccountsService which is unable to create a session file for the user - see https://bugzilla.redhat.com/show_bug.cgi?id=1718156
I realize that there may be use cases where this behaviour is absolutely necessary, so maybe it could be configured via pam_sss parameter or sssd configuration.