directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1003963 - in /websites/staging/directory/trunk/content: ./ api/user-guide/2-basic-ldap-api-usage.html api/user-guide/2.1-connection-disconnection.html api/user-guide/5-ldap-security.html
Date Mon, 02 Jan 2017 14:31:11 GMT
Author: buildbot
Date: Mon Jan  2 14:31:10 2017
New Revision: 1003963

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html
    websites/staging/directory/trunk/content/api/user-guide/2.1-connection-disconnection.html
    websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan  2 14:31:10 2017
@@ -1 +1 @@
-1776876
+1776939

Modified: websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html Mon
Jan  2 14:31:10 2017
@@ -184,12 +184,12 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
 <h1 id="2-basic-ldap-api-usage">2 - Basic LDAP API usage (...)<a class="headerlink"
href="#2-basic-ldap-api-usage" title="Permanent link">&para;</a></h1>
-<p>We provide three different set of methods to send requests to the <strong>LDAP</strong>
server :
-<em> A first set which is the simplest, where the methods don't return a response,
except the <em>search</em> and <em>compare</em> methods</em>
A second set, for advanced users, giving full control to the user
-* A third set allowing the user to send asynchronous requests.</p>
+<p>We provide three different sets of methods to send requests to the <strong>LDAP</strong>
server :
+<em> The first set is the simplest.  Its methods don't return a response, except for
the <em>search</em> and <em>compare</em> methods</em> The second
set is for advanced users and gives full control to the user
+* The third set allows users to send asynchronous requests.</p>
 <p>The first set of methods covers Bind, Add, Delete, Modify, Rename, Move, and Unbind
operations</p>
 <p>The second set covers MoveAndRename, Compare, Extended, controls.</p>
-<p>the third set covers the same methods, but ran in asynchronous mode.</p>
+<p>the third set covers the same methods, but runs in asynchronous mode.</p>
 <h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent
link">&para;</a></h2>
 <ul>
 <li><a href="2.1-connection-disconnection.html">2.1 - Connection and disconnection</a></li>

Modified: websites/staging/directory/trunk/content/api/user-guide/2.1-connection-disconnection.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/2.1-connection-disconnection.html
(original)
+++ websites/staging/directory/trunk/content/api/user-guide/2.1-connection-disconnection.html
Mon Jan  2 14:31:10 2017
@@ -184,7 +184,7 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
 <h1 id="21-connection-and-disconnection">2.1 - Connection and disconnection<a class="headerlink"
href="#21-connection-and-disconnection" title="Permanent link">&para;</a></h1>
-<p><strong>LDAP</strong> is a protocol which requires users to be connected
- and likely identified (authenticated) - before sending requests to the server. This connection
can potentially be maintained forever. What makes the <strong>LDAP</strong> protocol
different from, say, the <strong>HTTP</strong> protocol is that the connections
are issued explicitly. Here's we'll see how that is done.</p>
+<p>The <strong>LDAP</strong> is a protocol requires users to be connected,
and likely identified (authenticated), before sending requests to the server. This connection
can potentially be maintained forever. What makes the <strong>LDAP</strong> protocol
different from, say, the <strong>HTTP</strong> protocol is that the connections
are issued explicitly. Here we'll see how it's done.</p>
 <h2 id="opening-a-connection">Opening a connection<a class="headerlink" href="#opening-a-connection"
title="Permanent link">&para;</a></h2>
 <p>We can open a secure or a standard connection. </p>
 <h3 id="standard-connection">Standard connection<a class="headerlink" href="#standard-connection"
title="Permanent link">&para;</a></h3>

Modified: websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html Mon Jan 
2 14:31:10 2017
@@ -184,16 +184,16 @@
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover
> .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink
{ visibility: visible }</style>
 <h1 id="5-ldap-security">5 - LDAP Security<a class="headerlink" href="#5-ldap-security"
title="Permanent link">&para;</a></h1>
-<p>LDAP stores critical informations, and that needs to be secured. The Apache LDAP
API provides a way to access those data, there is little we can do to protect the access to
those data, but we can at least make it impossible for a third party to capture the transiting
data.</p>
-<p>Generally speaking when it comes to securing a system, we are addressing the three
<strong>A</strong>s :
+<p>LDAP databases store critical information that must be kept secure and the Apache
LDAP API can be used to access it a secure way while in flight.  It can't protect the data
while at rest -- that's for the database system itself to do.</p>
+<p>Generally speaking when it comes to securing a system, we are addressing the three
<strong>A</strong>s:
 <em> Authentication
 </em> Authorization
 * Auditing</p>
-<p>The only aspect we will focus on is the <strong>Authentication</strong>
part, because the <strong>LDAP</strong> protocol does not address the two other
aspects, when it comes to an <strong>API</strong>. We will shortly talk about
authorization in the last chapter.</p>
-<p>An additional aspect is encryption :
+<p>The only aspect we will focus on is the <strong>Authentication</strong>
part, because the <strong>LDAP</strong> protocol does not address the other two,
when it comes to an <strong>API</strong>. We will talk about authorization a little
bit in the last chapter.</p>
+<p>Another aspect of security is encryption:
 - securing the communication between the client and the server
 - password hash</p>
-<p>Last, not least, we have seen that we can bind on a <strong>LDAP</strong>
server using a name and a password, but there are other ways to bind, using <strong>SASL</strong>.
We will also explain how to use certificates in SSL/StartTLS.</p>
+<p>Last, but not least, we have seen how to perform a simple bind to an <strong>LDAP</strong>
server using a name and a password.  There are other ways to bind, using <strong>SASL</strong>.
We will also explain how to use certificates in SSL/StartTLS.</p>
 <h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent
link">&para;</a></h2>
 <ul>
 <li><a href="user-guide/5.1-ssl.html">5.1 - SSL (e)</a></li>



Mime
View raw message