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 7191418605 for ; Sat, 23 Jan 2016 22:41:21 +0000 (UTC) Received: (qmail 12563 invoked by uid 500); 23 Jan 2016 22:41:21 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 12516 invoked by uid 500); 23 Jan 2016 22:41:21 -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 12507 invoked by uid 99); 23 Jan 2016 22:41:21 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Jan 2016 22:41:21 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id C4EEDDFF8E; Sat, 23 Jan 2016 22:41:20 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: smckinney@apache.org To: commits@directory.apache.org Message-Id: X-Mailer: ASF-Git Admin Mailer Subject: directory-fortress-realm git commit: last of the readme cleanup Date: Sat, 23 Jan 2016 22:41:20 +0000 (UTC) Repository: directory-fortress-realm Updated Branches: refs/heads/master 76fdb415a -> 828b5ea8a last of the readme cleanup Project: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/repo Commit: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/commit/828b5ea8 Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/tree/828b5ea8 Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/diff/828b5ea8 Branch: refs/heads/master Commit: 828b5ea8a6742fd1ec4bb093dc2173834a5d41a5 Parents: 76fdb41 Author: Shawn McKinney Authored: Sat Jan 23 15:45:28 2016 -0600 Committer: Shawn McKinney Committed: Sat Jan 23 15:45:28 2016 -0600 ---------------------------------------------------------------------- README.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/directory-fortress-realm/blob/828b5ea8/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index ece38b8..181dce0 100755 --- a/README.md +++ b/README.md @@ -88,17 +88,20 @@ Everything else covered in steps that follow. Tested on Debian, Centos & Window ------------------------------------------------------------------------------- ## SECTION 3. Instructions for Application Usage -There are two options for web app usage. The first, pulls extra dependencies onto the Web app's classpath. The second, externalizes the dependencies from the Web app into a separate folder. + There are two options for web app usage of the fortress realm and there are pros and cons of each: -### Table of Options + * **Option 1** requires web apps to be dependent on the fortress realm jars but enables RBAC programmatic authZ controls. + It also allows multiple realms to be enabled within a single instance of Tomcat. + + * **Option 2** frees the web app from entanglement with additional dependencies, which is easier to manage, but limits capabilities to Java EE security control. It also limits the usage to a single realm enabled globally + which might not agree with multitenant deployments. -There are pros and cons of each. Option 1 requires web apps to be dependent on the fortress realm jars but enables RBAC programmatic authZ. Option 2, on the other hand, -frees the app of entanglement with fortress, which is easier to manage, but limits capabilities to Java EE security semantics. +### Table of Options -|Realm Type|Is Web App Dependent?|Is Declarative?|Is RBAC?|Is Global Security?| -|:--------:|:-------------------:|:-------------:|:------:|:-----------------:| -| Option 1 | Yes | Yes | Yes | No | -| Option 2 | No | Yes | No | Yes | +|Realm Type|Is Web App Dependent?|Is Declarative?|Is RBAC?|Is Global Security?|Multiple Realms Supported?| +|:--------:|:-------------------:|:-------------:|:------:|:-----------------:|:-------------------------: +| Option 1 | Yes | Yes | Yes | No | Yes | +| Option 2 | No | Yes | No | Yes | No | ### Option 1. For Single Web Context *enable Java EE security for a single web app running under Tomcat*