diff options
author | Pavel Březina <pbrezina@redhat.com> | 2017-10-20 11:49:26 +0200 |
---|---|---|
committer | Pavel Březina <pbrezina@redhat.com> | 2017-10-24 10:00:11 +0200 |
commit | 614b1cc9fc755e0d2ea5aaf9e64e1bf3ad135960 (patch) | |
tree | 614e60cc35c8b65357f452089b5d6caf888e4f32 | |
parent | 6ef14c5c9e16c4a660b5029cd2b6220496a36407 (diff) | |
download | sssd-sudoman.tar.gz sssd-sudoman.tar.xz sssd-sudoman.zip |
sudo: document background activitysudoman
When we introduced socket activation, we changed the internall behaviour.
Previously we disabled sudo if it was not listed in services, with
socket activation we removed this feature. Some users were confused
so this change documents current behaviour.
-rw-r--r-- | src/man/sssd.conf.5.xml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/src/man/sssd.conf.5.xml b/src/man/sssd.conf.5.xml index 7752e4508..13ff0d1ec 100644 --- a/src/man/sssd.conf.5.xml +++ b/src/man/sssd.conf.5.xml @@ -2348,6 +2348,14 @@ pam_account_locked_message = Account locked, please contact help desk. <manvolnum>5</manvolnum> </citerefentry>. </para> + <para> + <emphasis>NOTE:</emphasis> Sudo rules are + periodically downloaded in the background unless + the sudo provider is explicitly disabled. Set + <emphasis>sudo_provider = None</emphasis> to + disable all sudo-related activity in SSSD if you do + not want to use sudo with SSSD at all. + </para> </listitem> </varlistentry> <varlistentry> |