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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/2219
At this moment shell fallback mechanism in SSSD works a bit complex. Before it can be used you need to point in sssd.conf parameter allowed_shells. This parameter used for enumerate shells for which SSSD will use its shell fallback.
It's not very convenient when you got huge heterogeneous network for different projects with different administrators. It seems shells(5) would be enough to indicate whenever SSSD need to use fallback shell.
To resolve this problem I contributed a tiny patch https://lists.fedorahosted.org/pipermail/sssd-devel/2014-January/018265.html "it's not pretty but it got it going on"
Comment 3Nirupama Karandikar
2015-01-07 09:27:16 UTC
Tested with sssd-1.12.2-39.el7.x86_64
1. Set sssd.conf with following.
[nss]
debug_level = 9
allowed_shells = /bin/zsh
shell_fallback = /bin/bash
2. Add user in LDAP with "loginShell: /bin/zsh"
3. Make sure the 'zsh' rpm is not installed on client.
# getent -s sss passwd kb4
kb4:*:13581:13581:kb4:/home/kb4:/bin/bash
4. From /var/log/sssd/sssd_nss.log
-----------------------------
(Wed Jan 7 14:20:52 2015) [sssd[nss]] [nss_cmd_getpwnam_search] (0x0400): Returning info for user [kb4@DOMAIN1]
(Wed Jan 7 14:20:52 2015) [sssd[nss]] [get_shell_override] (0x0200): The shell '/bin/zsh' is allowed but does not exist. Using fallback
-----------------------------
5. Try login with user
# ssh kb4@localhost
kb4@localhost's password:
Last login: Wed Jan 7 14:32:23 2015 from localhost
id: cannot find name for group ID 13581
[kb4@dhcp207-182 ~]$ echo $SHELL
/bin/bash
[kb4@dhcp207-182 ~]$
6. Now install 'zsh' rpm on the system.
# yum install zsh
7 Re-try user lookup and auth.
# getent -s sss passwd kb4
kb4:*:13581:13581:kb4:/home/kb4:/bin/zsh
No shell fallback message will occur in logs allowed shell exist.
# ssh kb4@localhost
kb4@localhost's password:
[kb4@dhcp207-182]~% echo $SHELL
/bin/zsh
[kb4@dhcp207-182]~%
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-0441.html