docs: Multiple passdb backend support has been removed

[samba.git] / docs-xml / Samba3-ByExample / SBE-2000UserNetwork.xml

diff --git a/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml b/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml
index 3b9976e3f4163685046fceb92f7baac4d68bd2cd..cfd6981758af422ff988deb3aa268015023c9de8 100644 (file)
--- a/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml
+++ b/docs-xml/Samba3-ByExample/SBE-2000UserNetwork.xml
@@ -572,7 +572,7 @@ productivity.</para>
        <indexterm><primary>LDAP</primary></indexterm>
        <indexterm><primary>LDAP</primary><secondary>backend</secondary></indexterm>
        <indexterm><primary>SID</primary></indexterm>
-       When Samba-3 is configured to use an LDAP backend, it stores the domain
+       When Samba is configured to use an LDAP backend, it stores the domain
        account information in a directory entry. This account entry contains the
        domain SID. An unintended but exploitable side effect is that this makes it
        possible to operate with more than one PDC on a distributed network.
@@ -658,7 +658,7 @@ productivity.</para>
        <indexterm><primary>LDAP</primary></indexterm>
        <indexterm><primary>UID</primary></indexterm>
        <indexterm><primary>GID</primary></indexterm>
-       Samba-3 has the ability to use multiple password (authentication and
+       Samba has the ability to use multiple password (authentication and
        identity resolution) backends. The diagram in <link linkend="chap7idres"/>
        demonstrates how Samba uses winbind, LDAP, and NIS, the traditional system
        password database. The diagram only documents the mechanisms for
@@ -679,9 +679,8 @@ productivity.</para>
        <indexterm><primary>mysqlsam</primary></indexterm>
        <indexterm><primary>LDAP</primary></indexterm>
        <indexterm><primary>distributed</primary></indexterm>
-       Samba is capable of using the <constant>smbpasswd</constant>,
-       <constant>tdbsam</constant>, <constant>xmlsam</constant>,
-       and <constant>mysqlsam</constant> authentication databases. The SMB
+       Samba is capable of using the <constant>smbpasswd</constant> and
+       <constant>tdbsam</constant>. The SMB
        passwords can, of course, also be stored in an LDAP ldapsam
        backend. LDAP is the preferred passdb backend for distributed network
        operations.
@@ -689,9 +688,7 @@ productivity.</para>
 
        <para>
        <indexterm><primary>passdb backend</primary></indexterm>
-       Additionally, it is possible to use multiple passdb backends
-       concurrently as well as have multiple LDAP backends. As a result, you
-       can specify a failover LDAP backend. The syntax for specifying a
+       You can specify a failover LDAP backend. The syntax for specifying a
        single LDAP backend in &smb.conf; is:
 <screen>
 ...
@@ -722,48 +719,6 @@ passdb backend = ldapsam:"ldap://master.abmas.biz \
        </figure>
        </para>
 
-       <para>
-       Some folks have tried to implement this without the use of double quotes. This is the type of entry they
-       created:
-<screen>
-...
-passdb backend = ldapsam:ldap://master.abmas.biz \
-                 ldapsam:ldap://slave.abmas.biz
-...
-</screen>
-       <indexterm><primary>contiguous directory</primary></indexterm>
-       The effect of this style of entry is that Samba lists the users
-       that are in both LDAP databases. If both contain the same information,
-       it results in each record being shown twice. This is, of course, not the
-       solution desired for a failover implementation. The net effect of this
-       configuration is shown in <link linkend="ch7dualadd"/>
-       </para>
-
-       <figure id="ch7dualadd">
-               <title>Samba Configuration to Use Dual LDAP Databases - Broken - Do Not Use!</title>
-               <imagefile scale="55">ch7-dual-additive-LDAP</imagefile>
-       </figure>
-
-       <para>
-       If, however, each LDAP database contains unique information, this may 
-       well be an advantageous way to effectively integrate multiple LDAP databases 
-       into one seemingly contiguous directory. Only the first database will be updated.
-       An example of this configuration is shown in <link linkend="ch7dualok"/>.
-       </para>
-
-       <figure id="ch7dualok">
-               <title>Samba Configuration to Use Two LDAP Databases - The result is additive.</title>
-               <imagefile scale="55">ch7-dual-additive-LDAP-Ok</imagefile>
-       </figure>
-
-       <note><para>
-       When the use of ldapsam is specified twice, as shown here, it is imperative
-       that the two LDAP directories must be disjoint. If the entries are for a
-       master LDAP server as well as its own slave server, updates to the LDAP
-       database may end up being lost or corrupted. You may safely use multiple
-       LDAP backends only if both are entirely separate from each other.
-       </para></note>
-
     <para>
        It is assumed that the network you are working with follows in a
        pattern similar to what was covered in <link linkend="happy"/>. The following steps
@@ -1093,7 +1048,6 @@ index default               sub
 <smbconfoption name="idmap backend">ldap://massive.abmas.biz</smbconfoption>
 <smbconfoption name="idmap uid">10000-20000</smbconfoption>
 <smbconfoption name="idmap gid">10000-20000</smbconfoption>
-<smbconfoption name="printer admin">root</smbconfoption>
 <smbconfoption name="printing">cups</smbconfoption>
 </smbconfblock>
 </example>
@@ -1272,7 +1226,7 @@ index default               sub
                <itemizedlist>
                        <listitem><para>
                        <indexterm><primary>LDAP</primary></indexterm><indexterm><primary>BDC</primary></indexterm>
-                       Where Samba-3 is used as a domain controller, the use of LDAP is an 
+                       Where Samba is used as a domain controller, the use of LDAP is an
                        essential component to permit the use of BDCs.
                        </para></listitem>