[
https://issues.apache.org/jira/browse/TC-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nir Sopher resolved TC-428.
---------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
> Tenancy based access control - Delivery Service API
> ---------------------------------------------------
>
> Key: TC-428
> URL: https://issues.apache.org/jira/browse/TC-428
> Project: Traffic Control
> Issue Type: Improvement
> 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 "delivery-service as a resource". We enforce access
> control via the API to the different users.
> We also add a naive change in the UI - presenting the logged in user only
> delivery-services users he has access to.
> This JIRA does not deal with indirect tenancy (e.g DS/Regex table) - we will
> deal with it in following JIRAs
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
