directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject directory-fortress-commander git commit: minor doc
Date Sat, 15 Oct 2016 13:56:46 GMT
Repository: directory-fortress-commander
Updated Branches:
  refs/heads/master 3fbafdddf -> 6bbec9a6e


minor doc


Project: http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/repo
Commit: http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/commit/6bbec9a6
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/tree/6bbec9a6
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/diff/6bbec9a6

Branch: refs/heads/master
Commit: 6bbec9a6e4654739fea55aab85aa4c1010ec79ca
Parents: 3fbafdd
Author: Shawn McKinney <smckinney@apache.org>
Authored: Sat Oct 15 08:35:32 2016 -0500
Committer: Shawn McKinney <smckinney@apache.org>
Committed: Sat Oct 15 08:35:32 2016 -0500

----------------------------------------------------------------------
 README-MULTITENANCY.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/blob/6bbec9a6/README-MULTITENANCY.md
----------------------------------------------------------------------
diff --git a/README-MULTITENANCY.md b/README-MULTITENANCY.md
index 51fe369..5f2a2b0 100644
--- a/README-MULTITENANCY.md
+++ b/README-MULTITENANCY.md
@@ -77,7 +77,7 @@ Why are there are two locations for setting the tenant id, [context.xml](https:/
 1. Expedience in loading the realm tenant id with the context.xml file and the spring beans
using fortress.properties because that is where properties for those components are usually
set.
 
 2. Security Control.  It is necessary to allow the realm to use one tenant context, e.g.
HOME, and the web app instance another, e.g. acme123.  For the why consider a use case.  One
where many customer web app instances run from within one or more instances of a container
(like Tomcat).
- Only corporate employees may administer security policies within the customer's web app
instances.  Allowing each component to run within a separate context allows this to occur.
 Of course we may want to enable the customer to administer their own data which is supported
as well (e.g. setting both to acme123).
+ Only corporate employees may administer security policies within the customer's web app
instances, not the customers themselves.  On the contraray, we may want to allow the customer
to administer their own security data in which case we'd set both to acme123.
 
 ___________________________________________________________________________________
 #### END OF README-MULTITENANCY
\ No newline at end of file


Mime
View raw message