[jira] [Updated] (TC-468) User tenancy based access control - Federation

["Nir Sopher (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TC-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nir Sopher updated TC-468:
--------------------------
    Description: 
We have recently added "tenancy" to the project. 
With tenancy, every resource have a tenant, where resource can be a delivery-service, a server (future) and even a user.
We are now starting to enforce access-control based on the resource tenancy. A user can manage a resource only if the resource is under the user tenancy.

This JIRA deals with another step of "user as a resource" - enforcing access control on the management of federations.
We still need to finalize the specification of this access control, maybe add tenancy to the federation itself,  and it would not be included in the first phase of tenancy introduction.

  was:
We have recently added "tenancy" to the project. 
With tenancy, every resource have a tenant, where resource can be a delivery-service, a server (future) and even a user.
We are now starting to enforce access-control based on the resource tenancy. A user can manage a resource only if the resource is under the user tenancy.

This JIRA deals with another step of "user as a resource" - enforcing via the API access control on the management to federations.
We still need to finalize the specification of this access control, maybe add tenancy to the federation itself,  and it would not be included in the first phase of tenancy introduction.


> User tenancy based access control - Federation
> ----------------------------------------------
>
>                 Key: TC-468
>                 URL: https://issues.apache.org/jira/browse/TC-468
>             Project: Traffic Control
>          Issue Type: Improvement
>          Components: Traffic Ops
>            Reporter: Nir Sopher
>
> We have recently added "tenancy" to the project. 
> With tenancy, every resource have a tenant, where resource can be a delivery-service, a server (future) and even a user.
> We are now starting to enforce access-control based on the resource tenancy. A user can manage a resource only if the resource is under the user tenancy.
> This JIRA deals with another step of "user as a resource" - enforcing access control on the management of federations.
> We still need to finalize the specification of this access control, maybe add tenancy to the federation itself,  and it would not be included in the first phase of tenancy introduction.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)