Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1167324 - pam_sss domains option: User auth should fail when domains=<emtpy value>
pam_sss domains option: User auth should fail when domains=<emtpy value>
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd (Show other bugs)
7.1
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Jakub Hrozek
Kaushik Banerjee
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-24 08:18 EST by Amith
Modified: 2015-03-10 02:43 EDT (History)
8 users (show)

See Also:
Fixed In Version: sssd-1.12.2-35.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 05:34:28 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0441 normal SHIPPED_LIVE sssd bug fix and enhancement update 2015-03-05 10:05:27 EST

  None (edit)
Description Amith 2014-11-24 08:18:03 EST
Description of problem:

Set nothing to pam_sss option "domains=" in /etc/pam.d/password-auth-ac file. Try to authenticate a trusted user and authentication succeeds. Also, following message gets logged in /var/log/secure file:

sshd[21815]: pam_sss(sshd:setcred): Missing argument to option domains.

Ideally trusted user auth should fail as arguments to domains option are missing and it is not clear which restricted domain pam service should authenticate against. An alternate solution is to provide information in man page as to what happens when domains=<empty value>. 

Version-Release number of selected component (if applicable):
sssd-1.12.2-12.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Configure SSSD client with LDAP domain and set empty value to "domains=" option in pam file. Edit the sssd.conf file as given below:

[sssd]
config_file_version = 2
domains = LDAP
services = nss, pam
sbus_timeout = 30

[pam]
debug_level = 0xFFF0
pam_trusted_users = user1
pam_public_domains = all

[domain/LDAP]
id_provider = ldap
auth_provider = ldap
debug_level = 5
cache_credentials = FALSE
ldap_uri = ldaps://seaspray.lab.eng.pnq.redhat.com
ldap_tls_cacert = /etc/openldap/certs/server.pem
ldap_search_base = dc=example,dc=com

2. Also, edit "auth" section of the /etc/pam.d/password-auth-ac in SSSD client as given below:

auth        required      pam_env.so
auth        sufficient    pam_unix.so nullok try_first_pass
auth        requisite     pam_succeed_if.so uid >= 1000 quiet_success
auth        sufficient    pam_sss.so use_first_pass domains=
auth        required      pam_deny.so

3. Execute trusted user auth as given below:

# ssh -l user1 localhost
usr1@localhost's password: 
Last login: Mon Nov 24 20:12:07 2014 from localhost
Could not chdir to home directory /home/usr1: No such file or directory
id: cannot find name for group ID 11111
-sh-4.2$ logout

Actual results:
User auth successful with the following message in secure file:

sshd[21815]: pam_sss(sshd:setcred): Missing argument to option domains.

Expected results:
Either user auth should fail with the above message OR Man page should be updated with relevant information as to which domain, PAM service is allowed to authenticate against when domains=<empty> 

Additional info:
Comment 2 Jakub Hrozek 2014-12-03 11:38:56 EST
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2516
Comment 3 Jakub Hrozek 2014-12-13 17:06:52 EST
* master: 134bff159119b0f62492133983ba637957e26fab
Comment 5 Amith 2014-12-17 05:00:31 EST
Verified the bug on SSSD Version: sssd-1.12.2-36.el7.x86_64

User auth fails as expected when domains is set with an empty value in the service pam file.
Comment 7 errata-xmlrpc 2015-03-05 05:34:28 EST
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

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