summaryrefslogtreecommitdiffstats
path: root/src/man/sssd.conf.5.xml
diff options
context:
space:
mode:
authorJakub Hrozek <jhrozek@redhat.com>2014-12-11 11:19:58 +0100
committerJakub Hrozek <jhrozek@redhat.com>2014-12-13 23:41:34 +0100
commite786e081edecabb8e8506dd3c5e668094827bc52 (patch)
tree32d3e2e8b8e1f8a85547c639721dbd9780f977dc /src/man/sssd.conf.5.xml
parent0620f73a3c4b494112b75eeedfed4933e231382f (diff)
downloadsssd-e786e081edecabb8e8506dd3c5e668094827bc52.tar.gz
sssd-e786e081edecabb8e8506dd3c5e668094827bc52.tar.xz
sssd-e786e081edecabb8e8506dd3c5e668094827bc52.zip
MAN: Misspelled username in pam_trusted_users is not fatal
The man page claimed that failing to resolve an user name results in failure to start SSSD, but it's not the case and shouldn't be, because marking a user as trusted only elevates privileges, so it's safe to ignore that failure. https://fedorahosted.org/sssd/ticket/2530 Reviewed-by: Pavel Reichl <preichl@redhat.com>
Diffstat (limited to 'src/man/sssd.conf.5.xml')
-rw-r--r--src/man/sssd.conf.5.xml5
1 files changed, 0 insertions, 5 deletions
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml
index 3525d78ca..2002ccc7c 100644
--- a/src/man/sssd.conf.5.xml
+++ b/src/man/sssd.conf.5.xml
@@ -907,11 +907,6 @@ fallback_homedir = /home/%u
the PAM responder even in case it is not in the
pam_trusted_users list.
</para>
- <para>
- Also please note that if there is a user name in
- pam_trusted_users list which fails to be resolved
- it will cause that SSSD will not be started.
- </para>
</listitem>
</varlistentry>
<varlistentry>