[
https://issues.apache.org/jira/browse/STRATOS-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139985#comment-14139985
]
ASF GitHub Bot commented on STRATOS-761:
----------------------------------------
GitHub user shirolk opened a pull request:
https://github.com/apache/stratos/pull/43
Adding in isPublic property to beans for tenant isolation requirements -
for STRATOS-761
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shirolk/stratos master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/stratos/pull/43.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #43
----
commit dc025ed9c6d8753300cfc98b9848e280f0b528f0
Author: Shiro <[email protected]>
Date: 2014-09-10T01:40:39Z
Adding in tenant isolation into the mock rest endpoint
commit d0b0c6346f1761908e3abfebe80442ded61dfa08
Author: Shiro <[email protected]>
Date: 2014-09-11T08:40:59Z
Adding in tenant isolation for definitions and public definitions for mock
commit 673b17a15d689e2411fc16d1b1b4029f95cce107
Author: Shiro <[email protected]>
Date: 2014-09-11T08:41:04Z
Merge remote-tracking branch 'upstream/master'
commit db95d88e5cbf56357096c1fca00f716332dc4b2d
Author: Shiro <[email protected]>
Date: 2014-09-15T05:03:58Z
Merge remote-tracking branch 'upstream/master'
commit 48df048214a64e9dc6071421ebf494e879f70e8b
Author: Shiro <[email protected]>
Date: 2014-09-19T04:22:10Z
Adding in isPublic property to beans
----
> Tenant isolation for policies and definitions
> ---------------------------------------------
>
> Key: STRATOS-761
> URL: https://issues.apache.org/jira/browse/STRATOS-761
> Project: Stratos
> Issue Type: New Feature
> Affects Versions: 4.1.0 M1, 4.1.0 M2
> Reporter: Shiroshica Kulatilake
> Assignee: Shiroshica Kulatilake
> Fix For: 4.1.0 M2
>
>
> Currently in Stratos there is no isolation tenant wise when creating
> policies and definitions and also when using these. With this feature the
> following should be possible.
> 1. Ability for tenants to create their own policies and definitions
> 2. When using policy and definitions - tenant users should be able to by
> default only see those policies/definitions created within that space
> 3. Ability to create publicly available policies and definitions by the super
> tenant - which could be used by all tenants
> 4. Ability to set quota's to policies, definitions and subscriptions for each
> tenant when creating the tenant
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
