directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r857761 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/ apacheds/advanced-ug/images/
Date Mon, 08 Apr 2013 17:32:24 GMT
Author: buildbot
Date: Mon Apr  8 17:32:24 2013
New Revision: 857761

Log:
Staging update by buildbot for directory

Added:
    websites/staging/directory/trunk/content/apacheds/advanced-ug/images/sasl-digest-md5-config.png
  (with props)
Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2-sasl-authn.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.2-sasl-cram-md5-authn.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.3-sasl-digest-md5-authn.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.4-sasl-gssapi-authn.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Apr  8 17:32:24 2013
@@ -1 +1 @@
-1465583
+1465691

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2-sasl-authn.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2-sasl-authn.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2-sasl-authn.html Mon
Apr  8 17:32:24 2013
@@ -172,6 +172,10 @@
 <p><img alt="ApacheDS supported SASL mechanisms" src="images/supported-sasl-mechanisms.png"
/></p>
 <p>Configuring this list can also be done using <strong>Studio ApacheDS Configuration</strong>
plugin :</p>
 <p><img alt="ApacheDS SASL mechanisms configuration" src="images/sasl-mechanisms-config.png"
/></p>
+<h2 id="usage-and-security">Usage and security</h2>
+<p>Most of teh existing <strong>SASL</strong> mechanisms are just either
useless (<strong>PLAIN</strong>, <strong>ANONYMOUS</strong>) or too
weak to be used in a secured environement (<strong>DIGEST-MD5</strong> or <strong>CRAM-MD5</strong>).</p>
+<p>A new <strong>SASL</strong> mechanism has been designed to replace the
last two mechanisms : <strong>SCRAM</strong> (<a href="http://www.ietf.org/rfc/rfc5802.txt">RFC
5802</a>).</p>
+<p>In any case, if you are using one of those mechanisms, be sure to activate <strong>TLS</strong>.</p>
 <h2 id="specifications">Specifications</h2>
 <p>The SASL specifications are defined by an <a href="http://datatracker.ietf.org/wg/sasl/">IETF
Working Group</a> which has published the following proposed standards :</p>
 <div class="codehilite"><pre><span class="o">*</span> <span class="p">[</span><span
class="n">RFC</span> <span class="mi">4013</span><span class="p">](</span><span
class="n">http:</span><span class="sr">//</span><span class="n">www</span><span
class="o">.</span><span class="n">ietf</span><span class="o">.</span><span
class="n">org</span><span class="sr">/rfc/</span><span class="n">rfc4013</span><span
class="o">.</span><span class="n">txt</span><span class="p">)</span>
<span class="p">:</span> <span class="n">SASLprep:</span> <span
class="n">Stringprep</span> <span class="n">Profile</span> <span class="k">for</span>
<span class="n">User</span> <span class="n">Names</span> <span
class="ow">and</span> <span class="n">Passwords</span> 

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.2-sasl-cram-md5-authn.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.2-sasl-cram-md5-authn.html
(original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.2-sasl-cram-md5-authn.html
Mon Apr  8 17:32:24 2013
@@ -140,6 +140,10 @@
 <h1 id="4122-sasl-cram-md5-authentication">4.1.2.2 - SASL CRAM-MD5 Authentication</h1>
 <p>The <strong>CRAM-MD5</strong> <strong>SASL</strong> mechanism
is defined by <a href="http://www.ietf.org/rfc/rfc2195.txt">RFC 2195</a>.</p>
 <p>We will have an exchange between the client, which will send an empty <em>Bind
request</em> (ie, the username and credentials won't be sent the first time), and the
server will return a challenge.</p>
+<p><DIV class="warn" markdown="1">
+It's not recommanded to use this mechanism.
+</DIV></p>
+<h2 id="usage">Usage</h2>
 <p>The client first send a <em>BindRequest</em> with no credentials:</p>
 <div class="codehilite"><pre>MessageType : BIND_REQUEST
 Message ID : 1

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.3-sasl-digest-md5-authn.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.3-sasl-digest-md5-authn.html
(original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.3-sasl-digest-md5-authn.html
Mon Apr  8 17:32:24 2013
@@ -138,6 +138,84 @@
 
 
 <h1 id="4123-sasl-digest-md5-authentication">4.1.2.3 - SASL DIGEST-MD5 Authentication</h1>
+<p>The <strong>DIGEST-MD5</strong> <strong>SASL</strong> mechanism
is defined by <a href="http://www.ietf.org/rfc/rfc2829.txt">RFC 2829</a>, which
has been moved to an <em>historic</em> status by <a href="http://www.ietf.org/rfc/rfc6631.txt">RFC
6331</a>, due to its intrinsec weaknesses.</p>
+<p><DIV class="warn" markdown="1">
+It's not recommanded to use this mechanism.
+</DIV></p>
+<h2 id="usage">Usage</h2>
+<p>As for <strong>CRAM-MD5</strong> mechanism, there is an exchange between
the server and the client. First, the client sends a <em>BindRequest</em> with
no credentials :</p>
+<div class="codehilite"><pre>MessageType : BIND_REQUEST
+Message ID : 1
+    BindRequest
+        Version : &#39;3&#39;
+        Name : &#39;null&#39;
+        Sasl credentials
+            Mechanism :&#39;DIGEST-MD5&#39;
+            Credentials : null
+</pre></div>
+
+
+<p>The server respons with a <em>BindResponses</em> containing a challenge
:</p>
+<div class="codehilite"><pre>MessageType : BIND_RESPONSE
+Message ID : 2
+    BindResponse
+        Ldap Result
+            Result code : (SUCCESS) success
+            Matched Dn : &#39;&#39;
+            Diagnostic message : &#39;&#39;
+        Server sasl credentials : &#39;0x72 0x73 0x70 0x61 0x75 0x74 0x68 0x3D 0x37 0x36
0x32 0x64 0x30 0x37 0x32 0x32 0x37 0x64 0x39 0x32 0x33 0x63 0x38 0x38 0x38 0x32 0x64 0x35
0x65 0x63 0x34 0x38 0x30 0x37 0x66 0x36 0x66 0x33 0x34 0x65 &#39;
+</pre></div>
+
+
+<p>The client then compute the credentials, which contains many informations, some
of them being digested with the server's provided data :</p>
+<div class="codehilite"><pre>MessageType : BIND_REQUEST
+Message ID : 2
+    BindRequest
+        Version : &#39;3&#39;
+        Name : &#39;null&#39;
+        Sasl credentials
+            Mechanism :&#39;DIGEST-MD5&#39;
+            Credentials : (omitted-for-safety)
+</pre></div>
+
+
+<p>Here, the credentials content is encoded a a byte[], representing those data :</p>
+<div class="codehilite"><pre>charset = utf-8
+username = &quot;hnelson&quot;
+realm = &quot;example.com&quot;
+nonce = &quot;XVss/yPp4ZToAItV2acf5jgCYU1ALDNoUzGSqJZA&quot; 
+nc = 00000001
+cnonce = &quot;rQRG4H27HqvdjDVh1OhtrtYD88daWWdvfAj9XGl2&quot;
+digest-uri = &quot;ldap/localhost&quot;
+maxbuf = 65536 
+response = ef 63 c3 b9 c3 76 7e e6 c8 4b eb e7 7b 6e d4 56, 
+qop = auth
+</pre></div>
+
+
+<p>One of the big difference with <strong>CRAM-MD5</strong> is that we
send a <em>realm</em> (<strong>example.com</strong> here), which must
be configured on the server and on the client.</p>
+<p>The authentication requires 3 pieces of information on the client side :</p>
+<div class="codehilite"><pre><span class="o">*</span> <span class="n">the</span>
<span class="n">userName</span>
+<span class="o">*</span> <span class="n">the</span> <span class="n">realm</span>
+<span class="o">*</span> <span class="n">the</span> <span class="n">user</span>
<span class="n">password</span>
+</pre></div>
+
+
+<h2 id="server-configuration">Server configuration</h2>
+<p>There are a few parameters we need to configure on the server to allow this mechanism
to work. First, we need to define the <em>searchBaseDn</em>, which describes where
will the server look for entries having the <strong>UID</strong> attributeType.
This is a part of the <em>ldapServer</em> configuration :</p>
+<p><img alt="ApacheDS SASL searchBaseDn Configuration" src="images/sasl-digest-md5-config.png"
/></p>
+<p>This parameter (<em>ads_searchBaseDn</em> attributeType) can be found
on the following entry :</p>
+<div class="codehilite"><pre>ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config
+</pre></div>
+
+
+<p>You also have to configure the <strong>SaslRealms</strong> which is
also contained into the same entry (<em>ads_saslrealms</em> attributeType)</p>
+<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.
+</DIV></p>
+<p><DIV class="warn" markdown="1">
+The password must be stored in clear text on the server. This is a serious weakness...
+</DIV></p>
 
 
     <div class="nav">

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.4-sasl-gssapi-authn.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.4-sasl-gssapi-authn.html
(original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.4-sasl-gssapi-authn.html
Mon Apr  8 17:32:24 2013
@@ -130,7 +130,7 @@
         </div>
         <div class="nav_next">
         
-            <a href="4.1.2.3-sasl-cram-md5-authn.html">4.1.2.3 - SASL CRAM-MD5 Authentication</a>
+            <a href="4.1.2.5-sasl-external-authn.html">4.1.2.5 - SASL EXTERNAL Authentication</a>
 		
         </div>
         <div class="clearfix"></div>
@@ -158,7 +158,7 @@
         </div>
         <div class="nav_next">
         
-            <a href="4.1.2.3-sasl-cram-md5-authn.html">4.1.2.3 - SASL CRAM-MD5 Authentication</a>
+            <a href="4.1.2.5-sasl-external-authn.html">4.1.2.5 - SASL EXTERNAL Authentication</a>
 		
         </div>
         <div class="clearfix"></div>

Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/images/sasl-digest-md5-config.png
==============================================================================
Binary file - no diff available.

Propchange: websites/staging/directory/trunk/content/apacheds/advanced-ug/images/sasl-digest-md5-config.png
------------------------------------------------------------------------------
    svn:mime-type = image/png



Mime
View raw message