directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r985801 - in /websites/staging/directory/trunk/content: ./ fortress/overview.html
Date Sat, 16 Apr 2016 05:13:09 GMT
Author: buildbot
Date: Sat Apr 16 05:13:08 2016
New Revision: 985801

Staging update by buildbot for directory

    websites/staging/directory/trunk/content/   (props changed)

Propchange: websites/staging/directory/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Sat Apr 16 05:13:08 2016
@@ -1 +1 @@

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 Sat Apr 16 05:13:08 2016
@@ -168,7 +168,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="fortress-overview">Fortress Overview<a class="headerlink" href="#fortress-overview"
title="Permanent link">&para;</a></h1>
-<p>FORTRESS is a standards-based access management system that provides role-based
access control, delegated administration and password policies APIs and servivces.  It uses
LDAP for its data storage.</p>
+<p>FORTRESS is a standards-based access management system that provides role-based
access control, delegated administration and password policy services with an LDAP backend.</p>
 <h2 id="whats-in-it">What's in it?<a class="headerlink" href="#whats-in-it" title="Permanent
 <p>Included are the following components:</p>
@@ -177,9 +177,9 @@ h2:hover > .headerlink, h3:hover > .head
 <li>Rest  - HTTP protocol wrappers for the APIs</li>
 <li>Web   - HTML pages for the APIs</li>
-<p>It is released under terms of the Apache License 2.0. </p>
+<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>
-<p>To learn more, check out the quickstarts:</p>
+<p>To learn, check out the quickstarts:</p>
 <li><a href=""></a>
- Install Core for use with APACHEDS</li>
 <li><a href=""></a>
- Install Core for use with OPENLDAP</li>
@@ -188,15 +188,15 @@ h2:hover > .headerlink, h3:hover > .head
 <li><a href=""></a>
- Install Fortress Rest to Tomcat</li>
 <li><a href=""></a>
- Install Fortress Web to Tomcat</li>
-<p>Other README's:</p>
+<p>Other Guides:</p>
 <li><a href=""></a>
- How Fortress Multitenancy works</li>
 <li><a href=""></a>
- How the Fortress Config subsystem works</li>
 <h2 id="what-technologies-at-play">What technologies at play?<a class="headerlink"
href="#what-technologies-at-play" title="Permanent link">&para;</a></h2>
-<p>Fortress products run on open system hardware and software platforms supporting
LDAPv3, HTTP/S &amp; Java technologies. Functionality that extend beyond LDAPv3 is realized
via OpenLDAP/ApacheDS specific features. With the advent of Rest and Web products, <a href="http://tomcat">Apache
Tomcat</a>, or preferred Java servlet container is used to process HTTP
communications between endpoints.  </p>
+<p>Fortress products run on open system hardware and software platforms supporting
LDAPv3, HTTP &amp; Java.  </p>
 <h2 id="what-standards-apply">What standards apply?<a class="headerlink" href="#what-standards-apply"
title="Permanent link">&para;</a></h2>
-<p>The following technology standards are applied within Fortress...</p>
+<p>The following standards are implemented...</p>
 <h3 id="ansi-role-based-access-control-incits-359">ANSI Role-Based Access Control (INCITS
359)<a class="headerlink" href="#ansi-role-based-access-control-incits-359" title="Permanent
 <p>There is more to RBAC than assigning users to groups and applying ACL policies within
directories or databases.  <a href="">RBAC</a>
systems provide selective Role activation/deactivation, role hierarchies, and constraints
over separation of duty.  The <a href="">RBAC</a>
component provides APIs to add, update, delete, and search the directory data</p>
 <p>More info can be found on <a href="user-guide/1-intro-rbac.html">Intro to
ANSI RBAC Page</a></p>
@@ -213,9 +213,9 @@ h2:hover > .headerlink, h3:hover > .head
 <p>The Fortress Temporal model allows Users and Roles to carry time and date Constraints
which govern when activations may occur. Role constraints are checked on every call into Fortress.
 The user constraint applied only at session creation.</p>
 <h3 id="ansi-rbac-policy-enhanced-incits-494-2012">ANSI RBAC Policy-Enhanced (INCITS-494-2012)<a
class="headerlink" href="#ansi-rbac-policy-enhanced-incits-494-2012" title="Permanent link">&para;</a></h3>
 <p>One day.</p>
-<h2 id="what-security-services-are-available">What security services are available?<a
class="headerlink" href="#what-security-services-are-available" title="Permanent link">&para;</a></h2>
+<h2 id="what-services-are-available">What services are available?<a class="headerlink"
href="#what-services-are-available" title="Permanent link">&para;</a></h2>
 <p>Over one hundred services divided across the Manager components.</p>
-<p>A description of the managers follow with their javadoc links...</p>
+<p>A description of these managers follow along with their associated javadoc links
that describe the apis...</p>
 <h3 id="rbac-managers">RBAC Managers<a class="headerlink" href="#rbac-managers"
title="Permanent link">&para;</a></h3>
 <li><a href="">AccessMgr.html</a>
- Performs runtime access control operations on objects that are provisioned RBAC entities
that reside in LDAP directory.</li>

View raw message