docs-xml/winbindnssinfo: clarify interaction with idmap_ad etc.
authorBjörn Jacke <bjacke@samba.org>
Tue, 7 Jan 2020 09:21:18 +0000 (10:21 +0100)
committerRalph Boehme <slow@samba.org>
Wed, 8 Jan 2020 15:37:45 +0000 (15:37 +0000)
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14122
RN: docs: clarify interaction between winbind nss info and idmap backend

Signed-off-by: Bjoern Jacke <bjacke@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>
Autobuild-User(master): Ralph Böhme <slow@samba.org>
Autobuild-Date(master): Wed Jan  8 15:37:46 UTC 2020 on sn-devel-184

docs-xml/smbdotconf/winbind/winbindnssinfo.xml

index d8347442a8daf5716899e49e55d3ee4e346fba93..e6d17c256a15b3d1210bf10c6c7063ad86d34dc9 100644 (file)
                        Domain Controller does support the Microsoft "Services for Unix" (SFU)
                        LDAP schema, winbind can retrieve the login shell and the home
                        directory attributes directly from your Directory Server. For SFU 3.0 or 3.5 simply choose
-                       "sfu", if you use SFU 2.0 please choose "sfu20". Note that
-                       retrieving UID and GID from your ADS-Server requires to
-                       use <parameter moreinfo="none">idmap config DOMAIN:backend</parameter> = ad
-                       as well. The primary group membership is currently
-                       always calculated via the "primaryGroupID" LDAP attribute.
+                       "sfu", if you use SFU 2.0 please choose "sfu20".</para>
+                       <para>Note that for the idmap backend <refentrytitle>idmap_ad</refentrytitle>
+                       you need to configure those settings in the idmap configuration section.
+                       Make sure to consult the documentation of the idmap backend that you are using.
                        </para>
                </listitem>
        </itemizedlist>