directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r857421 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/4.1-authentication.html apacheds/advanced-ug/
Date Fri, 05 Apr 2013 17:34:04 GMT
Author: buildbot
Date: Fri Apr  5 17:34:04 2013
New Revision: 857421

Staging update by buildbot for directory

    websites/staging/directory/trunk/content/   (props changed)

Propchange: websites/staging/directory/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr  5 17:34:04 2013
@@ -1 +1 @@

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1-authentication.html
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1-authentication.html
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1-authentication.html
Fri Apr  5 17:34:04 2013
@@ -153,6 +153,7 @@
 <li><a href=""> - SASL CRAM-MD5 Authentication</a></li>
 <li><a href=""> - SASL DIGEST-MD5 Authentication</a></li>
 <li><a href=""> - SASL EXTERNAL Authentication</a></li>
+<li><a href=""> - SASL NTLM Authentication</a></li>
 <li><a href="4.1.3-kerberos-authn.html">4.1.3 - Kerberos authentication</a></li>

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/
Fri Apr  5 17:34:04 2013
@@ -138,6 +138,15 @@
 <h1 id="4122-sasl-plain-authentication"> SASL PLAIN Authentication</h1>
+<p>The <strong>PLAIN</strong> authentication is most certainly useless,
as one can already authenticate using the Simple Bind. However, it's still possible to issue
a SASL PLAIN authentication on <em>ApacheDS</em>.</p>
+<p>The difference with a Simple Bind is that the user's name is not  <strong>DN</strong>,
but a meaningful value that is stored into one of the user's entry Attributes.</p>
+<p>When the server receives a <strong>SASL PLAIN</strong> bind request,
it will look for the first entry which <strong>uid</strong> is equal to the provided
value, starting from the server <strong>searchBaseDN</strong> position in the
+<p><DIV class="note" markdown="1">
+ApacheDS expect the given name to be stored in the <strong>UID</strong> Attribute.
This is not configurable in this version of the server.
+<p><DIV class="note" markdown="1">
+ApacheDS does not yet support the authorization identity parameter.
     <div class="nav">

View raw message