Return-Path: X-Original-To: apmail-directory-commits-archive@www.apache.org Delivered-To: apmail-directory-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B612E17308 for ; Wed, 15 Apr 2015 20:59:05 +0000 (UTC) Received: (qmail 52737 invoked by uid 500); 15 Apr 2015 20:58:56 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 52685 invoked by uid 500); 15 Apr 2015 20:58:56 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 52676 invoked by uid 99); 15 Apr 2015 20:58:56 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2015 20:58:56 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id 2146DAC0051 for ; Wed, 15 Apr 2015 20:58:56 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r947777 - in /websites/staging/directory/trunk/content: ./ fortress/overview.html Date: Wed, 15 Apr 2015 20:58:56 -0000 To: commits@directory.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150415205856.2146DAC0051@hades.apache.org> Author: buildbot Date: Wed Apr 15 20:58:55 2015 New Revision: 947777 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 Wed Apr 15 20:58:55 2015 @@ -1 +1 @@ -1673955 +1673956 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 Wed Apr 15 20:58:55 2015 @@ -198,7 +198,7 @@

The following technology standards are applied within Fortress...

ANSI Role-Based Access Control (INCITS 359)

There is more to compliance than assigning users to groups and applying ACL policies within directories or databases. RBAC systems provide selective Role activation/deactivation, role hierarchies, and constraints over separation of duty. The RBAC component provides APIs to add, update, delete, and search the directory data. Fortress provides everything that is needed to exploit the full power of this ANSI specification.

-

More info can be found on Intro to ANSI RBAC Page

+

More info can be found on Intro to ANSI RBAC Page

Java EE Platform (tm) Security

Used for SSL, X.509 mutual authentication, form-based container authentication, coarse-grained authorization, SSO and more. Works within compliant Java Web apps like EnMasse policy server. Java EE security is good because its declarative controls keep the development and integration costs low. At the same time, it provides adequate network system security and the business apps run fast due to caching maintained within the app server container. This reduces costs because of fewer round-trips between the application and policy servers.

Administrative Role-Based Access Control (ARBAC02)