1PAM_SSS(8) SSSD Manual pages PAM_SSS(8)
2
6 pam_sss - PAM module for SSSD
7
9 pam_sss.so [quiet] [forward_pass] [use_first_pass] [use_authtok]
10 [retry=N] [ignore_unknown_user] [ignore_authinfo_unavail]
11 [domains=X] [allow_missing_name]
12
14 pam_sss.so is the PAM interface to the System Security Services daemon
15 (SSSD). Errors and results are logged through syslog(3) with the
16 LOG_AUTHPRIV facility.
17
19 quiet
20 Suppress log messages for unknown users.
21 forward_pass
23 If forward_pass is set the entered password is put on the stack for
24 other PAM modules to use.
25 use_first_pass
27 The argument use_first_pass forces the module to use a previous
28 stacked modules password and will never prompt the user - if no
29 password is available or the password is not appropriate, the user
30 will be denied access.
31 use_authtok
33 When password changing enforce the module to set the new password
34 to the one provided by a previously stacked password module.
35 retry=N
37 If specified the user is asked another N times for a password if
38 authentication fails. Default is 0.
39 Please note that this option might not work as expected if the
41 application calling PAM handles the user dialog on its own. A
42 typical example is sshd with PasswordAuthentication.
43 ignore_unknown_user
45 If this option is specified and the user does not exist, the PAM
46 module will return PAM_IGNORE. This causes the PAM framework to
47 ignore this module.
48 ignore_authinfo_unavail
50 Specifies that the PAM module should return PAM_IGNORE if it cannot
51 contact the SSSD daemon. This causes the PAM framework to ignore
52 this module.
53 domains
55 Allows the administrator to restrict the domains a particular PAM
56 service is allowed to authenticate against. The format is a
57 comma-separated list of SSSD domain names, as specified in the
58 sssd.conf file.
59 NOTE: Must be used in conjunction with the “pam_trusted_users” and
61 “pam_public_domains” options. Please see the sssd.conf(5) manual
62 page for more information on these two PAM responder options.
63 allow_missing_name
65 The main purpose of this option is to let SSSD determine the user
66 name based on additional information, e.g. the certificate from a
67 Smartcard.
68 The current use case are login managers which can monitor a
70 Smartcard reader for card events. In case a Smartcard is inserted
71 the login manager will call a PAM stack which includes a line like
72 auth sufficient pam_sss.so allow_missing_name
74 In this case SSSD will try to determine the user name based on the
77 content of the Smartcard, returns it to pam_sss which will finally
78 put it on the PAM stack.
79
81 All module types (account, auth, password and session) are provided.
82
84 If a password reset by root fails, because the corresponding SSSD
85 provider does not support password resets, an individual message can be
86 displayed. This message can e.g. contain instructions about how to
87 reset a password.
88 The message is read from the file pam_sss_pw_reset_message.LOC where
90 LOC stands for a locale string returned by setlocale(3). If there is no
91 matching file the content of pam_sss_pw_reset_message.txt is displayed.
92 Root must be the owner of the files and only root may have read and
93 write permissions while all other users must have only read
94 permissions.
95 These files are searched in the directory
97 /etc/sssd/customize/DOMAIN_NAME/. If no matching file is present a
98 generic message is displayed.
99
101 sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5),
102 sssd-ipa(5), sssd-ad(5), sssd-sudo(5), sss_cache(8), sss_debuglevel(8),
103 sss_groupadd(8), sss_groupdel(8), sss_groupshow(8), sss_groupmod(8),
104 sss_useradd(8), sss_userdel(8), sss_usermod(8), sss_obfuscate(8),
105 sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8),
106 sss_ssh_knownhostsproxy(8), sssd-ifp(5), pam_sss(8). sss_rpcidmapd(5)
107
109 The SSSD upstream - http://fedorahosted.org/sssd
110SSSD 01/15/2019 PAM_SSS(8)