directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r843836 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/3.1-administrative-points.html apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html apacheds/basic-ug/1.1-what-apacheds-is.html vision.html
Date Wed, 26 Dec 2012 04:02:55 GMT
Author: buildbot
Date: Wed Dec 26 04:02:54 2012
New Revision: 843836

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/advanced-ug/3.1-administrative-points.html
    websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html
    websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html
    websites/staging/directory/trunk/content/vision.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 26 04:02:54 2012
@@ -1 +1 @@
-1425764
+1425812

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/3.1-administrative-points.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/3.1-administrative-points.html
(original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/3.1-administrative-points.html
Wed Dec 26 04:02:54 2012
@@ -158,9 +158,9 @@ way they impact their associated Adminis
 <li><em>AAPs</em> manage an <em>AA</em> as if all the possible
type of <em>SAP</em> where declared
 for this area</li>
 <li><em>SAPs</em> manage an <em>AA</em> with respect to one
specific kind of role (Access
-Control, Collective Attributes, SubSchema or Trigger Execution )</li>
+Control, Collective Attributes, SubSchema or Trigger Execution)</li>
 <li>IAPs manage an <em>AA</em> inside another <em>AP</em></li>
-<li>An <em>AAP</em> or a <em>SAP</em> start at some point in
the tree, and all the entries
+<li>An <em>AAP</em> or a <em>SAP</em> starts at some point
in the tree, and all the entries
 below this <em>AAP</em>/<em>SAP</em> aren't related to any other
<em>AAP</em>. That also means
 that if an <em>AAP</em>/<em>SAP</em> is created below an existing
AP, then all the
 entries it covers are unlinked from the previous AP (except that for <em>SAP</em>,

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html
(original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html
Wed Dec 26 04:02:54 2012
@@ -127,13 +127,15 @@
 
 
 <h1 id="operations">Operations</h1>
-<p>There are six kind of operations we can have on an AdministrativePoint :
-<em> creating a new AP
-</em> removing an existing AP
-<em> modifying an existing AP by adding or removing a role
-</em> renaming an AP
-<em> moving an AP
-</em> renaming or moving an AP</p>
+<p>There are six kind of operations we can have on an AdministrativePoint :</p>
+<ul>
+<li>creating a new AP</li>
+<li>removing an existing AP</li>
+<li>modifying an existing AP by adding or removing a role</li>
+<li>renaming an AP</li>
+<li>moving an AP</li>
+<li>renaming or moving an AP</li>
+</ul>
 <p>Renaming an AP has no impact on the administrative model, as we don't point
 (internally) on the entry's DN, but on its UUID, so the last three
 operations can be gathered into one single Move operation.</p>
@@ -177,21 +179,23 @@ consistent.</p>
 with each of those modifications one by one.</p>
 <h3 id="addition-of-roles">Addition of roles</h3>
 <p>For this modification, we will have to check for each of the roles the very
-same elements than for the Add operation above :
-<em> if the entry does not have an AdministrativeRole AT, we have to create it
-</em> we must have at least one value
-<em> the role must be syntaxicaly correct
-</em> it should not already exist into the attribute
-<em> we can't add it if we already have an AAP role
-</em> we can't add it if it's an IAP and a SAP with the same role exists
-* if it's an IAP, it must have a parent AAP or SAP with the same role</p>
+same elements than for the Add operation above :</p>
+<ul>
+<li>if the entry does not have an AdministrativeRole AT, we have to create it</li>
+<li>we must have at least one value</li>
+<li>the role must be syntaxicaly correct</li>
+<li>it should not already exist into the attribute</li>
+<li>we can't add it if we already have an AAP role</li>
+<li>we can't add it if it's an IAP and a SAP with the same role exists</li>
+<li>if it's an IAP, it must have a parent AAP or SAP with the same role</li>
+</ul>
 <p>If all of those checks are ok, we can update the AP cache, which must be
 cloned, otherwise we may have to rollback the operation if any of the
 following modification fails.</p>
 <h3 id="removing-of-roles">Removing of roles</h3>
 <p>First, if there is no value for this modification, then that means we must
 delete the Attribute. This case will be analyzed later.
-For each of the role to remove, we have to apply those checks :
+For each of the roles to remove, we have to apply those checks :
 <em> the role must be syntaxicaly correct
 </em> it must already exist into the attribute
 * we can't remove an AAP or a SAP if there is a direct IAP in one of its

Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html Wed
Dec 26 04:02:54 2012
@@ -142,22 +142,22 @@
 </ul>
 </div>
 <h2 id="system-vision">System vision</h2>
-<p>ApacheDS 1.5 is an embeddable, extendable, standards compliant, modern LDAP server
written entirely in Java, and available under the Apache Software License. Other network protocols
like Kerberos and NTP are supported as well (and even more may be added), but basically (and
especially for this introduction guide) ApacheDS is an LDAP server.</p>
+<p>ApacheDS 2.0 is an embeddable, extendable, standards compliant, modern LDAP server
written entirely in Java, and available under the Apache Software License. Other network protocols
like Kerberos and NTP are supported as well (and even more may be added), but basically (and
especially for this introduction guide) ApacheDS is an LDAP server.</p>
 <p><em>Embeddable</em> means that it is possible to configure, start and
stop ApacheDS from other Java components, especially application servers, and the server runs
within the same VM. The solution has already been successfully embedded in Apache Geronimo,
JBoss, and others. The fact that the server is embeddable is quite interesting, nevertheless
you also have the deployment option to run the server standalone, for instance as a Windows
service. Perhaps you know this situation from other LDAP servers -- open source (like OpenLDAP)
as well as commercial ones (like Sun Java System Directory Server). This guide is dedicated
to people that are new to ApacheDS.  The guide concentrates on installing, configuring and
running ApacheDS in a standalone configuration.</p>
 <p><em>Extendable</em> means that the modern architecture of the solution
provides many extension points. Write your own partitions to store directory data, interceptors
to add functionality, etc. by implementing certain interfaces and plugging them in using Spring.</p>
-<p><em>Standard compliant</em> means that ApacheDS 1.5 adheres to all RFCs
relevant to LDAPv3. Please note that version 1.0 of the server has been successfully certified
by the Open Group in September 2006 ("LDAP certified"). Thus LDAP clients may rightly expect
that ApacheDS behaves like they expect.</p>
+<p><em>Standard compliant</em> means that ApacheDS 2.0 adheres to all RFCs
relevant to LDAPv3. Please note that version 1.0 of the server has been successfully certified
by the Open Group in September 2006 ("LDAP certified"). Thus LDAP clients may rightly expect
that ApacheDS behaves like they expect.</p>
 <p><em>Modern</em> means that ApacheDS aims modernize the LDAP territory,
as well as it favors standards compliance. New rich integration tier constructs like LDAP
Stored Procedures and Triggers are being built on top of existing standards.</p>
 <p><em>Entirely written in Java</em> means that the software compiles and
runs on a huge number of hardware and software platforms. Native installers are available
for Windows, MacOS and Solaris (both SPARC and intel platform), but in fact the set of possible
targets is by far more extensive.</p>
 <h3 id="architectural-overview">Architectural overview</h3>
 <p><img alt="50k ft architecture" src="images/50k-ft-architecture.png" /></p>
 <h2 id="origin-and-motives">Origin and Motives</h2>
 <p>Through his experiences with enterprise LDAP directories, Alex Karasulu, realized
there is a great need for rich integration tier constructs like LDAP Stored Procedures, Triggers,
and Views.  In 2001 he set out to alter the OpenLDAP server to offer support for these useful
facilities which are present in relational databases but missing in the LDAP world.  Alex's
attempts failed due to the complexity of the software which was brittle, and difficult to
manage.  As C code ported to several platforms, the OpenLDAP code base, had several #IFDEF
conditional pre-compiler directives that made it difficult to change the code.  At this point
Alex thought about implementing a new LDAP server in pure Java.  Thanks to NIO this was finally
possible using the 1.4 JDK. </p>
-<p>In October 2002 Alex Karasulu founded and registered the [LDAPd|http://sourceforge.net/projects/ldapd]
project at SourceForge.net.  LDAPd was a a pure Java embeddable LDAP v3 protocol daemon built
on the Avalon framework.  Alex donated the code to the Apache Software Foundation and the
code entered the [Apache Incubator|http://incubator.apache.org/|Apache Incubator Homepage]
in October 2003.  One year later in October of 2004, the Apache Directory Top Level Project
(TLP) was formed after a successful incubation with the now called Apache Directory Server
as its flagship product. After 4 years of development, in October 2006, Apache Directory Server
1.0 was released as an Open Group certified LDAPv3 protocol server. The certification has
been renewed in September 2007.</p>
+<p>In October 2002 Alex Karasulu founded and registered the <a href="http://sourceforge.net/projects/ldapd">LDAPd</a>
project at SourceForge.net.  LDAPd was a a pure Java embeddable LDAP v3 protocol daemon built
on the Avalon framework.  Alex donated the code to the Apache Software Foundation and the
code entered the <a href="http://incubator.apache.org/">Apache Incubator</a> in
October 2003.  One year later in October of 2004, the Apache Directory Top Level Project (TLP)
was formed after a successful incubation with the now called Apache Directory Server as its
flagship product. After 4 years of development, in October 2006, Apache Directory Server 1.0
was released as an Open Group certified LDAPv3 protocol server. The certification has been
renewed in September 2007.</p>
 <p>Having a standards compliant and modern LDAP server, Apache Directory Team is now
working on Identity and Access Management solutions leveraging the directory technology.</p>
 <h2 id="resources">Resources</h2>
 <ul>
-<li><a href="http://directory.apache.org/community%26resources/proposal-for-an-apache-directory-project.html">Proposal
for an Apache Directory Project</a> the original proposal for incubation, September
2003.</li>
-<li><a href="http://directory.apache.org/community%26resources/ldap-renaissance.html">Architecting
the Modern LDAP Renaissance: The Apache Directory Vision</a>, Paper for 1st International
Conference on LDAP, September 2007.</li>
+<li><a href="../../original-project-proposal.html">Proposal for an Apache Directory
Project</a> the original proposal for incubation, September 2003.</li>
+<li><a href="../../vision.html">Architecting the Modern LDAP Renaissance: The
Apache Directory Vision</a>, Paper for 1st International Conference on LDAP, September
2007.</li>
 </ul>
 
 

Modified: websites/staging/directory/trunk/content/vision.html
==============================================================================
--- websites/staging/directory/trunk/content/vision.html (original)
+++ websites/staging/directory/trunk/content/vision.html Wed Dec 26 04:02:54 2012
@@ -121,8 +121,20 @@
 
 <h1 id="architecting-the-modern-ldap-renaissance-the-apache-directory-vision">Architecting
the Modern LDAP Renaissance: The Apache Directory Vision</h1>
 <p>by Alex Karasulu, Founder of the <a href="http://directory.apache.org">Apache
Directory Project</a>, October 2002
-This paper was later, in September 2007, submitted to and accepted by the <a href="http://www.guug.de/veranstaltungen/ldapcon2007/">1st
International Conference on LDAP</a>, Cologne (Germany)
-[TOC]</p>
+This paper was later, in September 2007, submitted to and accepted by the <a href="http://www.guug.de/veranstaltungen/ldapcon2007/">1st
International Conference on LDAP</a>, Cologne (Germany)</p>
+<div class="toc">
+<ul>
+<li><a href="#architecting-the-modern-ldap-renaissance-the-apache-directory-vision">Architecting
the Modern LDAP Renaissance: The Apache Directory Vision</a><ul>
+<li><a href="#abstract">Abstract</a></li>
+<li><a href="#drivers-leading-to-the-birth-of-the-directory">Drivers Leading
to the Birth of the Directory</a></li>
+<li><a href="#demand-for-directories-should-be-high">Demand for Directories Should
Be High</a></li>
+<li><a href="#barriers-of-adoption">Barriers of Adoption</a></li>
+<li><a href="#renovating-ldap-directories-for-the-21st-century">Renovating (LDAP)
Directories for the 21st Century</a></li>
+<li><a href="#conclusion-the-aim-of-the-apache-directory-project">Conclusion:
The Aim of the Apache Directory Project</a></li>
+</ul>
+</li>
+</ul>
+</div>
 <h2 id="abstract">Abstract</h2>
 <div class="codehilite"><pre><span class="n">Directory</span> <span
class="n">technology</span> <span class="n">is</span> <span class="n">an</span>
<span class="n">indivisible</span> <span class="n">cornerstone</span>
<span class="n">in</span> <span class="n">computing</span> <span
class="n">science</span> <span class="ow">and</span> <span class="n">LDAP</span>
<span class="n">specifically</span> <span class="n">is</span> <span
class="n">essential</span> <span class="n">in</span> 
 <span class="n">several</span> <span class="n">industries</span>
<span class="n">however</span> <span class="n">it</span> <span
class="n">is</span> <span class="n">severely</span> <span class="n">underutilized</span><span
class="o">.</span>



Mime
View raw message