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: sp.
Date Tue, 08 Nov 2016 06:30:55 GMT
Repository: directory-fortress-commander
Updated Branches:
  refs/heads/master 4ab3328ae -> 42cc51bbc


sp.


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/42cc51bb
Tree: http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/tree/42cc51bb
Diff: http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/diff/42cc51bb

Branch: refs/heads/master
Commit: 42cc51bbc29012dfffa9b51cd74a83bcc46711fd
Parents: 4ab3328
Author: Shawn McKinney <smckinney@apache.org>
Authored: Tue Nov 8 00:30:48 2016 -0600
Committer: Shawn McKinney <smckinney@apache.org>
Committed: Tue Nov 8 00:30:48 2016 -0600

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


http://git-wip-us.apache.org/repos/asf/directory-fortress-commander/blob/42cc51bb/README-MULTITENANCY.md
----------------------------------------------------------------------
diff --git a/README-MULTITENANCY.md b/README-MULTITENANCY.md
index 5f2a2b0..9f77419 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, 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.
+ Only corporate employees may administer security policies within the customer's web app
instances, not the customers themselves.  On the contrary, 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