Staff permissions are not enough to create/edit/delete builds in Capomastro

Bug #1421655 reported by Caio Begotti
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

As of today anyone who needs to create or edit or delete a build (be it a project or a dependency one) need Django's superuser powers to do so. The staff permissions, which I would expect to be enough for this, is not used at all and is handled exactly the same as regular users in Capomastro. We would need to tweak this to allow a fine-grained control of accounts so different access levels are actually respected.

Tags: story
Revision history for this message
Daniel Manrique (roadmr) wrote :

Looks like all the permissions infrastructure is in place, we need to add permissions checking in the proper views/models. This is well-described so setting to triaged.

Changed in capomastro:
milestone: none → 2015-05
importance: Undecided → Medium
status: New → Triaged
tags: added: story
Daniel Manrique (roadmr)
Changed in capomastro:
milestone: 2015-05 → 2015-07
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.