Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating an invalidate content request (purge) on a delivery service should check tenancy (if turned on) #1171

Closed
mitchell852 opened this issue Sep 13, 2017 · 1 comment · Fixed by #1186
Assignees
Labels
bug something isn't working as intended Traffic Ops related to Traffic Ops
Milestone

Comments

@mitchell852
Copy link
Member

mitchell852 commented Sep 13, 2017

The following API route is used to create an "Invalidate content" (aka purge request) on a delivery service:

$r->post("/api/$version/user/current/jobs")->over( authenticated => 1, not_ldap => 1 )->to( 'Job#create_current_user_job', namespace => $namespace );

This route current checks:

if role is ops (or higher) OR if delivery service is assigned to user.

instead it should follow this logic:

if (use_tenancy = 1) { check tenancy on delivery service }
else { check if role is ops (or higher) OR if delivery service is assigned to user }

@mitchell852 mitchell852 added bug something isn't working as intended Traffic Ops related to Traffic Ops Traffic Ops API labels Sep 13, 2017
@mitchell852 mitchell852 self-assigned this Sep 15, 2017
@mitchell852
Copy link
Member Author

@nir-sopher - i'm going to take a crack at this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended Traffic Ops related to Traffic Ops
Projects
None yet
1 participant