You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Nir Sopher (JIRA)" <ji...@apache.org> on 2017/08/09 14:48:00 UTC
[jira] [Resolved] (TC-463) Delivery-service&User tenancy based
access control - DS/User Assignment
[ https://issues.apache.org/jira/browse/TC-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nir Sopher resolved TC-463.
---------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
> Delivery-service&User tenancy based access control - DS/User Assignment
> -----------------------------------------------------------------------
>
> Key: TC-463
> URL: https://issues.apache.org/jira/browse/TC-463
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops
> Reporter: Nir Sopher
> Fix For: 2.1.0
>
>
> 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" as well as "user as a resource" - enforcing via the API access control on DS to User: The logged in user should have access to both the DS as well as the user assigned to it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)