[ https://issues.apache.org/jira/browse/TC-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nir Sopher updated TC-464: -------------------------- 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 "delivery-service as a resource" - enforcing access control on Federations. We still need to finalize the specification of this access control.the TC 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 "delivery-service as a resource" - enforcing via the API access control on Federations. We still need to finalize the specification of this access control.the TC > Delivery-service tenancy based access control - Federation > ---------------------------------------------------------- > > Key: TC-464 > URL: https://issues.apache.org/jira/browse/TC-464 > 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 "delivery-service as a resource" - > enforcing access control on Federations. > We still need to finalize the specification of this access control.the TC -- This message was sent by Atlassian JIRA (v6.4.14#64029)