svn commit: r1060958 - in /websites/staging/directory/trunk/content: ./ fortress/overview.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 26 18:20:40 2020
New Revision: 1060958

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/fortress/overview.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 26 18:20:40 2020
@@ -1 +1 @@
-1878124
+1878130

Modified: websites/staging/directory/trunk/content/fortress/overview.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/overview.html (original)
+++ websites/staging/directory/trunk/content/fortress/overview.html Tue May 26 18:20:40 2020
@@ -170,14 +170,14 @@
 }
 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="apache-fortress-overview">Apache Fortress Overview<a class="headerlink" href="#apache-fortress-overview" title="Permanent link">&para;</a></h1>
-<p>FORTRESS is a standards-based access management system, written in Java, that provides role-based access control, delegated administration and password policy services with LDAP.</p>
+<p>FORTRESS is a standards-based authorization system, that provides role-based access control, delegated administration and password policy services using an LDAP backend.</p>
 <h2 id="whats-in-it">What's in it?<a class="headerlink" href="#whats-in-it" title="Permanent link">&para;</a></h2>
 <p>Included are the following components:</p>
 <ul>
-<li>Core  - Java Access Management SDK</li>
+<li>Core  - Java Authorization SDK</li>
 <li>Realm - Java EE security for Apache Tomcat</li>
-<li>Rest  - HTTP protocol wrappers for the APIs</li>
-<li>Web   - HTML pages for the APIs</li>
+<li>Rest  - HTTP protocol wrappers for the APIs using Apache CXF</li>
+<li>Web   - HTML pages and framework for the APIs using Apache Wicket</li>
 </ul>
 <p>It's released under terms of the Apache License 2.0. </p>
 <h2 id="how-does-it-work">How Does It Work?<a class="headerlink" href="#how-does-it-work" title="Permanent link">&para;</a></h2>
@@ -211,7 +211,7 @@ h2:hover > .headerlink, h3:hover > .head
 <h3 id="administrative-role-based-access-control-arbac02">Administrative Role-Based Access Control (<a href="http://profsandhu.com/journals/tissec/p113-oh.pdf">ARBAC02</a>)<a class="headerlink" href="#administrative-role-based-access-control-arbac02" title="Permanent link">&para;</a></h3>
 <p>The ARBAC model explains how <a href="http://csrc.nist.gov/groups/SNS/rbac/documents/draft-rbac-implementation-std-v01.pdf">RBAC</a> can be extended with organizational controls to govern policies regarding the security administration process. ARBAC helps by allowing administrative tasks be delegated to end users who fall outside typical datacenter operations. </p>
 <h3 id="ietf-password-policies">IETF Password Policies<a class="headerlink" href="#ietf-password-policies" title="Permanent link">&para;</a></h3>
-<p>Fortress sully supports password policies of both ApacheDS and OpenLDAP.  It adds by integrating with its administrative and access control APIs.  These APIs enable outside apps to participate and manipulate OpenLDAP password policies without understanding the specifics of how they work. Fortress provides services for setting up new policies and ensuring password policies are tracked and enforced across all avenues.</p>
+<p>Fortress fully supports password policies of both ApacheDS and OpenLDAP.  It adds by integrating with its administrative and access control APIs.  These APIs enable outside apps to participate and manipulate OpenLDAP password policies without understanding the specifics of how they work. Fortress provides services for setting up new policies and ensuring password policies are tracked and enforced across all avenues.</p>
 <h3 id="auditing">Auditing<a class="headerlink" href="#auditing" title="Permanent link">&para;</a></h3>
 <p>Fortress audits use OpenLDAP's slapd access log overlay.</p>
 <p>The Fortress audits rely on slapd events to track its data exchanges performed within its own APIs.  Change event tracking includes adds, updates, and deletes of Fortress entities.  Read and search events tracked include user authentication, authorization, and policy interrogations.  Full historical data change tracking is maintained and may be searched later with APIs to be used for monitoring, reporting, and undo. The log may be retrieved later to synch with outside database for long-term regulatory and compliance concerns.  </p>