Skip to content
Permalink
Browse files
Some simple updates formatting and wording
  • Loading branch information
shawnmckinney committed Jul 16, 2021
1 parent d7fe566 commit 5a1b1725ec8bb9513e9173280606176ec7d033c2
Showing 3 changed files with 19 additions and 14 deletions.
@@ -7,9 +7,9 @@ slug: index
<div class="hero clearfix">
<div class="top">
<h1>Apache Fortress&trade;</h1>
<h2>Access Management SDK and Web Components</h2>
<h2>Authorization SDK and Web Components</h2>
<div class="description">
<b>A standards-based access management system, written in Java, supports ANSI INCITS 359 RBAC and more. </b>
<b>A standards-based authorization platform, written in Java, supports ANSI INCITS 359 RBAC and more. </b>
<br><br>
</div>
</div>
@@ -4,13 +4,18 @@ title: History

# Fortress History

In 2009 a small team of developers[1], who are brothers, began work on the *Open Access Manager* project. From its onset, the push behind this project was to build a fully functioning access control system that is based on open standards and wholly open source. In particular, Role-Based Access Control (ANSI INCITS 359) was a focal point, although that adherence brought with it a need for expanded coverage into other areas like auditing and administration. After a couple of years of coding in their spare time, the brothers unveiled the project at the 2011 LDAPCon in Heidelberg, and with it a new name - *Fortress*. At the same time, it was announced that the OpenLDAP foundation would sponsor the project and it would be released under a BSD-style variant of an Open Source Software license.
In 2009 a small team of developers[1], who are brothers, began work on the *Open Access Manager* project. From its onset, the push behind this project was to build a fully functioning access control system that is based on
open standards and wholly open source. In particular, Role-Based Access Control (ANSI INCITS 359) was a focal point, although that adherence brought with it a need for expanded coverage into other areas like auditing and administration. After a couple of years of coding in their spare time, the project was unveiled at the 2011 LDAPCon in Heidelberg[2], and with it a new name - *Fortress*. At the same time, it was announced that the OpenLDAP
foundation would sponsor the project and it would be released under a BSD-style variant of an Open Source Software license.

That first release, back in 2011, included just the fortress core and realm components, but development of the web interface (commander) and rest server (enmasse) was already underway. A few more years saw many more releases and the eventual completion of the others rounding out the entire product line into what's available today.
That first release, back in 2011, included just the fortress core and realm components, but development of the web interface (commander) and rest server (enmasse) was already underway. A few more years saw many more release
s and the eventual completion of the others rounding out the entire product line into what's available today.

Eventually, it was understood that nights and weekends of a few developers isn't enough and so if the fortress concept was to survive, it had to be carried into a larger field. In 2014 the Fortress project moved from its OpenLDAP foundation home into the ASF as a subproject of the Apache Directory.
Eventually, it was understood that nights and weekends of a few developers isn't enough and so if the fortress concept was to survive, it had to be carried into a larger field. In 2014 the Fortress project moved from its Op
enLDAP foundation home into the ASF as a subproject of the Apache Directory.

This new home proved worthy as the influx of new talent gained from being associated with the Apache Directory project, along with added exposure from its community has brought with it many gains and improvements.
This new home proved worthy as the influx of new talent gained from being associated with the Apache Directory project, along with added exposure from its community has brought with it many gains and improvements.

Footnotes:
[1]. team roster in 2009 consisted of Kelly McKinney (engineering manager), Kevin McKinney (fortress web developer), and Shawn McKinney (fortress core developer).
[1] Team roster in 2009: Kelly McKinney (engineering manager), Kevin McKinney (fortress web developer), and Shawn McKinney (fortress core developer).
[2] Presentation [Open Source IAM using Fortress and OpenLDAP](https://ldapcon.org/2011/index.php?site=open-source)
@@ -11,7 +11,7 @@ FORTRESS is a standards-based authorization system, that provides role-based acc
Included are the following components:

* Core - Java Authorization SDK
* Realm - Java EE security for Apache Tomcat
* Realm - Security provider for Apache Tomcat
* Rest - HTTP protocol wrappers for the APIs using Apache CXF
* Web - HTML pages and framework for the APIs using Apache Wicket

@@ -78,35 +78,35 @@ The Fortress Temporal model allows Users and Roles to carry time and date Constr

### ANSI RBAC Policy-Enhanced (INCITS-494-2012)

One day.
Not yet but does check attributes during the user-role activation phase as described in this LDAPCon presentation: [Towards an Attribute-Based Role-Based Access Control System](https://ldapcon.org/2019/wp-content/events/PGRNSN.htm)

## What services are available?

Over one hundred services divided across the Manager components.

A description of these managers follow along with their associated javadoc links that describe the apis...

###RBAC Managers
### RBAC Managers

* [AccessMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/AccessMgr.html) - Performs runtime access control operations on objects that are provisioned RBAC entities that reside in LDAP directory.
* [AdminMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/AdminMgr.html) - Performs administrative functions to provision Fortress RBAC entities into the LDAP directory.
* [ReviewMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/ReviewMgr.html) - The review functions on RBAC entities in LDAP.

###ARBAC Managers
### ARBAC Managers

* [DelAccessMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/DelAccessMgr.html) - Runtime delegated access control operations on objects that are provisioned Fortress ARBAC entities that reside in LDAP.
* [DelAdminMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/DelAdminMgr.html) - Policy administration of Fortress ARBAC entities in LDAP.
* [DelReviewMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/DelReviewMgr.html) - Policy review ops of ARBAC entities in LDAP.

###PW Policies Manager
### PW Policies Manager

* [PwPolicyMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/PwPolicyMgr.html) - Used to perform admin and review functions on the PWPOLICIES data sets.

###Audit Manager
### Audit Manager

* [AuditMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/AuditMgr.html) - Methods used to search OpenLDAP's slapd access log for fortress events.

###Config Manager
### Config Manager

* [ConfigMgr.html](https://directory.apache.org/fortress/gen-docs/latest/apidocs/org/apache/directory/fortress/core/ConfigMgr.html) - CRUD methods used to manage properties stored within LDAP.

0 comments on commit 5a1b172

Please sign in to comment.