[
https://issues.apache.org/jira/browse/TC-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nir Sopher updated TC-466:
--------------------------
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 static-dns-entry, according to their Delivery
service.
We still need to finalize the specification of this access control, and it
would not be included in the first phase of tenancy introduction, assuming that
the application hide from the user the ability to deal with entries of DSes
which are not under his tenancy.
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 static-dns-entry, according to their
Delivery service.
We still need to finalize the specification of this access control, and it
would not be included in the first phase of tenancy introduction, assuming that
the application hide from the user the ability to deal with entries of DSes
which are not under his tenancy.
> Delivery-service tenancy based access control - statidnsentry
> -------------------------------------------------------------
>
> Key: TC-466
> URL: https://issues.apache.org/jira/browse/TC-466
> 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 static-dns-entry, according to their Delivery
> service.
> We still need to finalize the specification of this access control, and it
> would not be included in the first phase of tenancy introduction, assuming
> that the application hide from the user the ability to deal with entries of
> DSes which are not under his tenancy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
