]> granicus.if.org Git - ejabberd/commitdiff
Remove the old note about LDAP lack of encryption.
authorBadlop <badlop@process-one.net>
Mon, 21 Dec 2009 16:10:51 +0000 (16:10 +0000)
committerBadlop <badlop@process-one.net>
Mon, 21 Dec 2009 16:10:51 +0000 (16:10 +0000)
SVN Revision: 2817

doc/guide.html
doc/guide.tex

index 9c34149576ecf9fdc725fe1cfc904c44c1df99fa..1fbc9499fcb1c022c9e1e69b0580532852c206b5 100644 (file)
@@ -1638,8 +1638,7 @@ value is <TT>""</TT>.
 {ldap_port, 389}.
 {ldap_rootdn, "cn=Manager,dc=domain,dc=org"}.
 {ldap_password, "secret"}.
-</PRE><P>Note that current LDAP implementation does not support SSL secured communication
-and SASL authentication.</P><P> <A NAME="ldapauth"></A> </P><!--TOC subsubsection Authentication-->
+</PRE><P>Note that current LDAP implementation does not support SASL authentication.</P><P> <A NAME="ldapauth"></A> </P><!--TOC subsubsection Authentication-->
 <H4 CLASS="subsubsection"><!--SEC ANCHOR --><A HREF="#ldapauth">Authentication</A></H4><!--SEC END --><P> <A NAME="ldapauth"></A> </P><P>You can authenticate users against an LDAP directory. Available options are:</P><DL CLASS="description"><DT CLASS="dt-description">
 <B><TT>{ldap_base, Base}</TT></B></DT><DD CLASS="dd-description">LDAP base directory which stores
 users accounts. This option is required.
index ebf8c9e54f680e5c420bbc4158756db32031968e..47e87daafddebc68462eb1930f53dfdf4ac2dca0 100644 (file)
@@ -2186,8 +2186,7 @@ Example:
 {ldap_password, "secret"}.
 \end{verbatim}
 
-Note that current LDAP implementation does not support SSL secured communication
-and SASL authentication.
+Note that current LDAP implementation does not support SASL authentication.
 
 \makesubsubsection{ldapauth}{Authentication}