You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Jeremy Mitchell (JIRA)" <ji...@apache.org> on 2017/07/28 17:40:00 UTC
[jira] [Commented] (TC-483) TPv2 / TO API - make tenant a required
field on delivery service
[ https://issues.apache.org/jira/browse/TC-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105347#comment-16105347 ]
Jeremy Mitchell commented on TC-483:
------------------------------------
Actually, changing the API to required tenant on delivery service create / update represents a breaking api change and cannot be done unless the API version is revved to 1.3 so I think this change should only be made in TPv2.
> TPv2 / TO API - make tenant a required field on delivery service
> ----------------------------------------------------------------
>
> Key: TC-483
> URL: https://issues.apache.org/jira/browse/TC-483
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops API, Traffic Portal
> Reporter: Jeremy Mitchell
> Priority: Minor
>
> Currently, the tenant_id on a delivery service create or update is optional in the Traffic Portal and the TO API. This presents a risk because failure to set the ds.tenant_id will allow all users to see that delivery service. This may include users that should have no access to this delivery service.
> I suggest we make this a required field on create or update of a ds. At some point tenancy will be required but in the interim tenancy can be turned off using the use-tenancy=0 parameter.
> If the desire is to not use tenancy, you can still set the ds.tenant = root tenant (which is provided via seeds.sql) and use-tenancy=0
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)