directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From elecha...@apache.org
Subject directory-fortress-core git commit: Fixed some Sonar warnings
Date Thu, 28 May 2015 07:29:26 GMT
Repository: directory-fortress-core
Updated Branches:
  refs/heads/master d72f03f23 -> b8ef81ca9


Fixed some Sonar warnings


Project: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/repo
Commit: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/commit/b8ef81ca
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/tree/b8ef81ca
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-core/diff/b8ef81ca

Branch: refs/heads/master
Commit: b8ef81ca93a23bd4ba9f4f24e998c7ca5408d40d
Parents: d72f03f
Author: Emmanuel L├ęcharny <elecharny@symas.com>
Authored: Thu May 28 09:29:18 2015 +0200
Committer: Emmanuel L├ęcharny <elecharny@symas.com>
Committed: Thu May 28 09:29:18 2015 +0200

----------------------------------------------------------------------
 .../directory/fortress/core/overview.html       | 122 +++++-----
 .../apache/directory/fortress/core/package.html | 227 ++++++++++---------
 2 files changed, 186 insertions(+), 163 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/b8ef81ca/src/main/java/org/apache/directory/fortress/core/overview.html
----------------------------------------------------------------------
diff --git a/src/main/java/org/apache/directory/fortress/core/overview.html b/src/main/java/org/apache/directory/fortress/core/overview.html
index 0872307..9d2cda4 100755
--- a/src/main/java/org/apache/directory/fortress/core/overview.html
+++ b/src/main/java/org/apache/directory/fortress/core/overview.html
@@ -18,59 +18,71 @@
  *
 -->
 <html>
-   <head>
-      <title>Overview of the org.apache.fortress.core component</title>
-   </head>
-   <body>
-       A standards based Identity and Access Management system for LDAP v3 compliant systems.
-       <hr>
-       <h2>How do I start using the Fortress?</h2>
-       <p>
-       <h3>Check out the <a href="org/apache/directory/fortress/core/doc-files/ten-minute-guide.html">Apache
Fortress Ten Minute Guide</a></h3>
-       <h4>Build fortress core, realm, web and rest components from source.  Covers
tomcat and apacheds server installation and configuration.</h4>
-       Designed to get going with apache fortress software in a short amount of time on Fedora
and Debian machines.
-       </p>
-       <hr>
-      <h2>What can Fortress Core SDK do?</h2>
-       Contained within this SDK are APIs and utilities to perform authentication, authorization,
administration, audit and password policies.
-       The most important package in this system is <A HREF="org/apache/directory/fortress/core/package-summary.html">org.apache.directory.fortress.core</A>
which contains all of the public APIs that are called by outside programs.
-      <h3>Fortress Manager APIs</h3>
-       <ol>
-       <li><a href="org/apache/directory/fortress/core/AccessMgr.html">AccessMgr</a>
- This class performs runtime access control operations on objects that are provisioned <a
href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a>
entities that reside in LDAP directory.</li>
-       <li><a href="org/apache/directory/fortress/core/AdminMgr.html">AdminMgr</a>
- This class performs administrative functions to provision Fortress <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a>
entities into the LDAP directory.</li>
-       <li><a href="org/apache/directory/fortress/core/AuditMgr.html">AuditMgr</a>
- This interface prescribes methods used to search OpenLDAP's slapd access log.</li>
-       <li><a href="org/apache/directory/fortress/core/DelAccessMgr.html">DelAccessMgr</a>
- This interface prescribes the API for performing runtime delegated access control operations
on objects that are provisioned Fortress <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>
entities that reside in LDAP directory.</li>
-       <li><a href="org/apache/directory/fortress/core/DelAdminMgr.html">DelAdminMgr</a>
- This class prescribes the <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>
DelegatedAdminMgr interface for performing policy administration of Fortress ARBAC entities
that reside in LDAP directory.</li>
-       <li><a href="org/apache/directory/fortress/core/DelReviewMgr.html">DelReviewMgr</a>
- This class prescribes the <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>
DelegatedReviewMgr interface for performing policy interrogation of provisioned Fortress ARBAC02
entities that reside in LDAP directory.</li>
-       <li><a href="org/apache/directory/fortress/core/PwPolicyMgr.html">PwPolicyMgr</a>
- This class adheres to <a href="http://tools.ietf.org/html/draft-behera-ldap-password-policy-10">IETF
PW policy draft</a> and is used to perform administrative and review functions on the
<a href="org/openldap/fortress/rbac/PwPolicy.html">PWPOLICIES</a> and <a href="org/openldap/fortress/rbac/User.html">USERS</a>
data sets within Fortress.</li>
-       <li><a href="org/apache/directory/fortress/core/ReviewMgr.html">ReviewMgr</a>
- This interface prescribes the administrative review functions on already provisioned Fortress
<a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a>
entities that reside in LDAP directory.</li>
-       </ol>
-       <h5>Error Handling</h5>
-       These APIs throw checked exceptions defined in <a href="org/apache/directory/fortress/core/SecurityException.html">SecurityException</a>
-       <hr>
-      <h2>What technologies are used?</h2>
-      <p>
-         Fortress SDK runs on any platform that supports Java technology and LDAP v3 protocols.
 Functionality that extends beyond
-          LDAP v3 is provided via <a href="http://openldap.org/">OpenLDAP</a>
or <a href="http://directory.apache.org/apacheds/">ApacheDS</a> specific features.
 In other words Fortress was optimized to run on OpenLDAP but works on any directory.
-      </p>
-       <hr>
-      <h2>What are the conditions of use?</h2>
-      <p>
-         This software development kit is open source, thus free to use and distribute via
the <a href="http://www.apache.org/licenses/">Apache License, Version 2.0</a>.
-         It was developed and tested on open systems like <a href="http://www.ubuntu.com/">Ubuntu</a>
and <a href="http://www.centos.org/">Centos</a> and was helped along
-         by the following open source products:
-          <ol>
-          <li><a href="http://www.openldap.org/project/">The OpenLDAP Project</a></li>
-          <li><a href="http://www.apache.org/">The Apache Software Foundation</a></li>
-          <li><a href="http://www.eigenbase.org/">The Eigenbase Project</a></li>
-          <li><a href="http://ehcache.org/">Ehcache</a></li>
-          </ol>
-      </p>
-       <hr>
-       <h2>Where are the coding samples?</h2>
-      <p>
-         The <A HREF="../samples/overview-summary.html">coding samples</A> are
located within the <b>org.apache.directory.fortress.core.samples</b> package.
 The samples show how Fortress apis work.  The
-         ant <b>dist</b> target in build.xml creates the samples package in the
/dist folder of this project and is intended to be used for experimentation.
-      </p>
-   </body>
+  <head>
+    <title>Overview of the org.apache.fortress.core component</title>
+  </head>
+  <body>
+    A standards based Identity and Access Management system for LDAP v3 compliant systems.
+    
+    <hr>
+    
+    <h2>How do I start using the Fortress?</h2>
+    <p>
+      <h3>Check out the <a href="org/apache/directory/fortress/core/doc-files/ten-minute-guide.html">Apache
Fortress Ten Minute Guide</a></h3>
+      <h4>Build fortress core, realm, web and rest components from source.  Covers
tomcat and apacheds server installation and configuration.</h4>
+      Designed to get going with apache fortress software in a short amount of time on Fedora
and Debian machines.
+    </p>
+     
+    <hr>
+    
+    <h2>What can Fortress Core SDK do?</h2>
+     Contained within this SDK are APIs and utilities to perform authentication, authorization,
administration, audit and password policies.
+     The most important package in this system is <A HREF="org/apache/directory/fortress/core/package-summary.html">org.apache.directory.fortress.core</A>
which contains all of the public APIs that are called by outside programs.
+ 
+    <h3>Fortress Manager APIs</h3>
+    <ol>
+      <li><a href="org/apache/directory/fortress/core/AccessMgr.html">AccessMgr</a>
- This class performs runtime access control operations on objects that are provisioned <a
href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a>
entities that reside in LDAP directory.</li>
+      <li><a href="org/apache/directory/fortress/core/AdminMgr.html">AdminMgr</a>
- This class performs administrative functions to provision Fortress <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a>
entities into the LDAP directory.</li>
+      <li><a href="org/apache/directory/fortress/core/AuditMgr.html">AuditMgr</a>
- This interface prescribes methods used to search OpenLDAP's slapd access log.</li>
+      <li><a href="org/apache/directory/fortress/core/DelAccessMgr.html">DelAccessMgr</a>
- This interface prescribes the API for performing runtime delegated access control operations
on objects that are provisioned Fortress <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>
entities that reside in LDAP directory.</li>
+      <li><a href="org/apache/directory/fortress/core/DelAdminMgr.html">DelAdminMgr</a>
- This class prescribes the <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>
DelegatedAdminMgr interface for performing policy administration of Fortress ARBAC entities
that reside in LDAP directory.</li>
+      <li><a href="org/apache/directory/fortress/core/DelReviewMgr.html">DelReviewMgr</a>
- This class prescribes the <a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>
DelegatedReviewMgr interface for performing policy interrogation of provisioned Fortress ARBAC02
entities that reside in LDAP directory.</li>
+      <li><a href="org/apache/directory/fortress/core/PwPolicyMgr.html">PwPolicyMgr</a>
- This class adheres to <a href="http://tools.ietf.org/html/draft-behera-ldap-password-policy-10">IETF
PW policy draft</a> and is used to perform administrative and review functions on the
<a href="org/openldap/fortress/rbac/PwPolicy.html">PWPOLICIES</a> and <a href="org/openldap/fortress/rbac/User.html">USERS</a>
data sets within Fortress.</li>
+      <li><a href="org/apache/directory/fortress/core/ReviewMgr.html">ReviewMgr</a>
- This interface prescribes the administrative review functions on already provisioned Fortress
<a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a>
entities that reside in LDAP directory.</li>
+    </ol>
+    
+    <h5>Error Handling</h5>
+    These APIs throw checked exceptions defined in <a href="org/apache/directory/fortress/core/SecurityException.html">SecurityException</a>
+    
+    <hr>
+    
+    <h2>What technologies are used?</h2>
+    <p>
+      Fortress SDK runs on any platform that supports Java technology and LDAP v3 protocols.
 Functionality that extends beyond
+      LDAP v3 is provided via <a href="http://openldap.org/">OpenLDAP</a> or
<a href="http://directory.apache.org/apacheds/">ApacheDS</a> specific features.
 In other words Fortress was optimized to run on OpenLDAP but works on any directory.
+    </p>
+       
+    <hr>
+      
+    <h2>What are the conditions of use?</h2>
+    <p>
+      This software development kit is open source, thus free to use and distribute via the
<a href="http://www.apache.org/licenses/">Apache License, Version 2.0</a>.
+      It was developed and tested on open systems like <a href="http://www.ubuntu.com/">Ubuntu</a>
and <a href="http://www.centos.org/">Centos</a> and was helped along
+      by the following open source products:
+      <ol>
+        <li><a href="http://www.openldap.org/project/">The OpenLDAP Project</a></li>
+        <li><a href="http://www.apache.org/">The Apache Software Foundation</a></li>
+        <li><a href="http://www.eigenbase.org/">The Eigenbase Project</a></li>
+        <li><a href="http://ehcache.org/">Ehcache</a></li>
+      </ol>
+    </p>
+       
+    <hr>
+       
+    <h2>Where are the coding samples?</h2>
+    <p>
+      The <A HREF="../samples/overview-summary.html">coding samples</A> are located
within the <b>org.apache.directory.fortress.core.samples</b> package.  The samples
show how Fortress apis work.  The
+      ant <b>dist</b> target in build.xml creates the samples package in the
/dist folder of this project and is intended to be used for experimentation.
+    </p>
+  </body>
 </html>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/directory-fortress-core/blob/b8ef81ca/src/main/java/org/apache/directory/fortress/core/package.html
----------------------------------------------------------------------
diff --git a/src/main/java/org/apache/directory/fortress/core/package.html b/src/main/java/org/apache/directory/fortress/core/package.html
index 12e5037..9fe698f 100755
--- a/src/main/java/org/apache/directory/fortress/core/package.html
+++ b/src/main/java/org/apache/directory/fortress/core/package.html
@@ -51,115 +51,126 @@
       There is also a lockout mechanism to temporarily bar entities from activating.
       AuditMgr may be used to interrogate OpenLDAP audit and historical information.
     </p>
+
     <hr>
-      <h2>Description of Package Contents</h2>
-      This package contains APIs to do the following
-      <ol>
-        <li>Role Based Access Control (RBAC)</li>
-        <li>Administrative Role Based Access Control (ARBAC)</li>
-        <li>Password Policies</li>
-        <li>Audit Trail</li>
-      </ol>
-      The following sections provides more info on each.
-      <hr>
-        <h3>1. Role Based Access Control description</h3>
-        <p>
-          Many of the method names and signatures within this package were taken directly
from ANSI INCITS 359-2004.
-          The RBAC Functional specification describes administrative operations for the creation
-          and maintenance of RBAC element sets and relations; administrative review functions
for
-          performing administrative queries; and system functions for creating and managing
-          RBAC attributes on user sessions and making access control decisions.
-        <p/>
-        <h4>RBAC0 - Core</h4>
-        Many-to-many relationship between Users, Roles and Permissions. Selective role activation
into sessions.  API to add, update, delete identity data and perform identity and access control
decisions during runtime operations.
-        <p/>
-        <img src="./doc-files/RbacCore.png"/>
-        <h4>RBAC1 - General Hierarchical Roles</h4>
-        Simplifies role engineering tasks using inheritance of one or more parent roles.
-        <p/>
-        <img src="./doc-files/RbacHier.png"/>
-        <h4>RBAC2 - Static Separation of Duty (SSD) Relations</h4>
-        Enforce mutual membership exclusions across role assignments.  Facilitate dual control
policies by restricting which roles may be assigned to users in combination.  SSD provide
added granularity for authorization limits which help enterprises meet strict compliance regulations.
-        <p/>
-        <img src="./doc-files/RbacSSD.png"/>
-        <h4>RBAC3 - Dynamic Separation of Duty (DSD) Relations</h4>
-        Control allowed role combinations to be activated within an RBAC session.  DSD policies
fine tune role policies that facilitate authorization dual control and two man policy restrictions
during runtime security checks.
-        <p/>
-        <img src="./doc-files/RbacDSD.png"/>
-        <p/>
-      </hr>
-      <hr>
-        <h3>2. Administrative Role Based Access Control (ARBAC) description</h3>
-        These APIs map directly to similar named APIs specified by ARBAC02 functions.  
-        The ARBAC Functional specification describes delegated administrative
-        operations for the creation and maintenance of ARBAC element sets and relations.
 
-        Delegated administrative review functions for performing administrative queries
-        and system functions for creating and managing ARBAC attributes on user sessions
and making delegated 
-        administrative access control decisions.
-        <h4>ARBAC02 Diagram</h4>
-        <img src="./doc-files/ARbac.png"/>
-        <p/>
-        Fortress fully supports the Oh/Sandhu/Zhang ARBAC02 model for delegated administration.
 
-        ARBAC provides large enterprises the capability to delegate administrative authority
to 
-        users that reside outside of the security admin group.
-        Decentralizing administration helps because it provides security provisioning capability
to 
-        work groups without sacrificing regulations for accountability or traceability.
-        <p/>
-      </hr>
-      <hr>
-        <h3>3. Password Policy description</h3>
-        Fortress APIs store and interrogate policies on <a href="http://www.openldap.org/">OpenLDAP</a>
which supports the 
-        IETF <a href="http://tools.ietf.org/html/draft-behera-ldap-password-policy-10/">Password
Policies LDAP directories</a> draft.  
-        Policies may be applied at the user, group or global level.
-        Password enforcement options include:
-        <ul>
-          <li>A configurable limit on failed authentication attempts.</li>
-          <li>A counter to track the number of failed authentication attempts.</li>
-          <li>A time frame in which the limit of consecutive failed authentication
attempts must happen before action is taken.</li>
-          <li>The action to be taken when the limit is reached. The action will either
be nothing, or the account will be locked.</li>
-          <li>An amount of time the account is locked (if it is to be locked) This
can be indefinite.</li>
-          <li>Password expiration.</li>
-          <li>Expiration warning</li>
-          <li>Grace authentications</li>
-          <li>Password history</li>
-          <li>Password minimum age</li>
-          <li>Password minimum length</li>
-          <li>Password Change after Reset</li>
-          <li>Safe Modification of Password</li>
-        </ul>
-        <h4>Password Policy diagram</h4>
-        The following is an example of policies that can be configured. There is no limit
to the number of different policies 
-        that can be created and enforced.
-        <p/>
-        <img src="./doc-files/PasswordPolicy.png"/>
-        <p/>
-      </hr>
-      <hr>
-        <h3>4. History and Audit trail using OpenLDAP</h3>
-        Provides an OpenLDAP access log retrieval mechanism that enables security event monitoring.
-        <ol>
-          <li>Authentication events:</li>
-          <li>Session enablement events</li>
-          <li>Authorization events</li>
-          <li>Entity mods and deletes</li>
-        </ol>
-        <h4>Diagram of Audit Events</h4>
-        <img src="./doc-files/Audit.png"/>
-        <p/>
-        All events include Fortress context, see {@code FortEntity}.
-        <p/>
-        <h4>The following APIs generate events subsequently stored in this access log:</h4>
-        <ul>
-          <li> {@link org.apache.directory.fortress.core.AccessMgr}</li>
-          <li> {@link org.apache.directory.fortress.core.AdminMgr}</li>
-          <li> {@link org.apache.directory.fortress.core.AdminMgr}</li>
-          <li> {@link org.apache.directory.fortress.core.DelAdminMgr}</li>
-          <li> {@link org.apache.directory.fortress.core.cfg.ConfigMgr}</li>
-          <li> {@link org.apache.directory.fortress.core.PwPolicyMgr}</li>
-        </ul>
-        </p>
-      </hr>
-    </hr>
+
+    <h2>Description of Package Contents</h2>
+    This package contains APIs to do the following
+    <ol>
+      <li>Role Based Access Control (RBAC)</li>
+      <li>Administrative Role Based Access Control (ARBAC)</li>
+      <li>Password Policies</li>
+      <li>Audit Trail</li>
+    </ol>
+    The following sections provides more info on each.
+
+    <hr>
+
+    <h3>1. Role Based Access Control description</h3>
+    <p>
+      Many of the method names and signatures within this package were taken directly from
ANSI INCITS 359-2004.
+      The RBAC Functional specification describes administrative operations for the creation
+      and maintenance of RBAC element sets and relations; administrative review functions
for
+      performing administrative queries; and system functions for creating and managing
+      RBAC attributes on user sessions and making access control decisions.
+    <p/>
+
+    <h4>RBAC0 - Core</h4>
+    Many-to-many relationship between Users, Roles and Permissions. Selective role activation
into sessions.  API to add, update, delete identity data and perform identity and access control
decisions during runtime operations.
+    <p/>
+    <img src="./doc-files/RbacCore.png"/>
+
+    <h4>RBAC1 - General Hierarchical Roles</h4>
+    Simplifies role engineering tasks using inheritance of one or more parent roles.
+    <p/>
+    <img src="./doc-files/RbacHier.png"/>
+
+    <h4>RBAC2 - Static Separation of Duty (SSD) Relations</h4>
+    Enforce mutual membership exclusions across role assignments.  Facilitate dual control
policies by restricting which roles may be assigned to users in combination.  SSD provide
added granularity for authorization limits which help enterprises meet strict compliance regulations.
+    <p/>
+    <img src="./doc-files/RbacSSD.png"/>
+
+    <h4>RBAC3 - Dynamic Separation of Duty (DSD) Relations</h4>
+    Control allowed role combinations to be activated within an RBAC session.  DSD policies
fine tune role policies that facilitate authorization dual control and two man policy restrictions
during runtime security checks.
+    <p/>
+    <img src="./doc-files/RbacDSD.png"/>
+    <p/>
+
+    <hr>
+
+    <h3>2. Administrative Role Based Access Control (ARBAC) description</h3>
+    These APIs map directly to similar named APIs specified by ARBAC02 functions.  
+    The ARBAC Functional specification describes delegated administrative
+    operations for the creation and maintenance of ARBAC element sets and relations.  
+    Delegated administrative review functions for performing administrative queries
+    and system functions for creating and managing ARBAC attributes on user sessions and
making delegated 
+    administrative access control decisions.
+    <h4>ARBAC02 Diagram</h4>
+    <img src="./doc-files/ARbac.png"/>
+    <p/>
+    Fortress fully supports the Oh/Sandhu/Zhang ARBAC02 model for delegated administration.
 
+    ARBAC provides large enterprises the capability to delegate administrative authority
to 
+    users that reside outside of the security admin group.
+    Decentralizing administration helps because it provides security provisioning capability
to 
+    work groups without sacrificing regulations for accountability or traceability.
+    <p/>
+
+    <hr>
+        
+    <h3>3. Password Policy description</h3>
+    Fortress APIs store and interrogate policies on <a href="http://www.openldap.org/">OpenLDAP</a>
which supports the 
+    IETF <a href="http://tools.ietf.org/html/draft-behera-ldap-password-policy-10/">Password
Policies LDAP directories</a> draft.  
+    Policies may be applied at the user, group or global level.
+    Password enforcement options include:
+    <ul>
+      <li>A configurable limit on failed authentication attempts.</li>
+      <li>A counter to track the number of failed authentication attempts.</li>
+      <li>A time frame in which the limit of consecutive failed authentication attempts
must happen before action is taken.</li>
+      <li>The action to be taken when the limit is reached. The action will either
be nothing, or the account will be locked.</li>
+      <li>An amount of time the account is locked (if it is to be locked) This can
be indefinite.</li>
+      <li>Password expiration.</li>
+      <li>Expiration warning</li>
+      <li>Grace authentications</li>
+      <li>Password history</li>
+      <li>Password minimum age</li>
+      <li>Password minimum length</li>
+      <li>Password Change after Reset</li>
+      <li>Safe Modification of Password</li>
+    </ul>
+    
+    <h4>Password Policy diagram</h4>
+    The following is an example of policies that can be configured. There is no limit to
the number of different policies 
+    that can be created and enforced.
+    <p/>
+    <img src="./doc-files/PasswordPolicy.png"/>
+    <p/>
+
+    <hr>
+    
+    <h3>4. History and Audit trail using OpenLDAP</h3>
+    Provides an OpenLDAP access log retrieval mechanism that enables security event monitoring.
+    <ol>
+      <li>Authentication events:</li>
+      <li>Session enablement events</li>
+      <li>Authorization events</li>
+      <li>Entity mods and deletes</li>
+    </ol>
+
+    <h4>Diagram of Audit Events</h4>
+    <img src="./doc-files/Audit.png"/>
+    <p/>
+    All events include Fortress context, see {@code FortEntity}.
+    <p/>
+    <h4>The following APIs generate events subsequently stored in this access log:</h4>
+    <ul>
+      <li> {@link org.apache.directory.fortress.core.AccessMgr}</li>
+      <li> {@link org.apache.directory.fortress.core.AdminMgr}</li>
+      <li> {@link org.apache.directory.fortress.core.AdminMgr}</li>
+      <li> {@link org.apache.directory.fortress.core.DelAdminMgr}</li>
+      <li> {@link org.apache.directory.fortress.core.cfg.ConfigMgr}</li>
+      <li> {@link org.apache.directory.fortress.core.PwPolicyMgr}</li>
+    </ul>
+    </p>
   </body>
 </html>
 


Mime
View raw message