Blame SOURCES/0023-MAN-Document-that-PAM-stack-contains-the-systemd-use.patch

d6181b
From 820151f3813f08c704cb87a99988fe39f9f48a8d Mon Sep 17 00:00:00 2001
d6181b
From: Jakub Hrozek <jhrozek@redhat.com>
d6181b
Date: Thu, 4 Jul 2019 10:22:25 +0200
d6181b
Subject: [PATCH] MAN: Document that PAM stack contains the systemd-user
d6181b
 service in the account phase in RHEL-8
d6181b
d6181b
Resolves:
d6181b
https://pagure.io/SSSD/sssd/issue/3932
d6181b
d6181b
Reviewed-by: Tomas Halman <thalman@redhat.com>
d6181b
---
d6181b
 src/man/sssd-ldap.5.xml | 8 ++++++++
d6181b
 1 file changed, 8 insertions(+)
d6181b
d6181b
diff --git a/src/man/sssd-ldap.5.xml b/src/man/sssd-ldap.5.xml
d6181b
index c205aea64..aca0f9e72 100644
d6181b
--- a/src/man/sssd-ldap.5.xml
d6181b
+++ b/src/man/sssd-ldap.5.xml
d6181b
@@ -834,6 +834,14 @@
d6181b
                             ldap_user_authorized_service option
d6181b
                             to work.
d6181b
                         </para>
d6181b
+                        <para>
d6181b
+                            Some distributions (such as Fedora-29+ or RHEL-8)
d6181b
+                            always include the <quote>systemd-user</quote> PAM
d6181b
+                            service as part of the login process. Therefore when
d6181b
+                            using service-based access control, the
d6181b
+                            <quote>systemd-user</quote> service might need to be
d6181b
+                            added to the list of allowed services.
d6181b
+                        </para>
d6181b
                         <para>
d6181b
                             Default: authorizedService
d6181b
                         </para>
d6181b
-- 
d6181b
2.20.1
d6181b