1 <samba:parameter name="client ldap sasl wrapping"
5 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
8 The <smbconfoption name="client ldap sasl wrapping"/> defines whether
9 ldap traffic will be signed or signed and encrypted (sealed).
10 Possible values are <emphasis>plain</emphasis>, <emphasis>sign</emphasis>
11 and <emphasis>seal</emphasis>.
15 The values <emphasis>sign</emphasis> and <emphasis>seal</emphasis> are
16 only available if Samba has been compiled against a modern
17 OpenLDAP version (2.3.x or higher).
21 This option is needed in the case of Domain Controllers enforcing
22 the usage of signed LDAP connections (e.g. Windows 2000 SP3 or higher).
23 LDAP sign and seal can be controlled with the registry key
24 "<literal>HKLM\System\CurrentControlSet\Services\</literal>
25 <literal>NTDS\Parameters\LDAPServerIntegrity</literal>"
26 on the Windows server side.
30 Depending on the used KRB5 library (MIT and older Heimdal versions)
31 it is possible that the message "integrity only" is not supported.
32 In this case, <emphasis>sign</emphasis> is just an alias for
33 <emphasis>seal</emphasis>.
37 The default value is <emphasis>plain</emphasis> which is not irritable
38 to KRB5 clock skew errors. That implies synchronizing the time
39 with the KDC in the case of using <emphasis>sign</emphasis> or
40 <emphasis>seal</emphasis>.
43 <value type="default">plain</value>