Story #7337
closed
Story #7338: [Epic] As a user, I have pulpcore enforcing Role Based Access Control
As a user, the orphan cleanup endpoint will support Role Based Access Control
0%
Description
Ticket moved to GitHub: "pulp/pulpcore/1924":https://github.com/pulp/pulpcore/issues/1924
By default no users will be able to run orphan cleanup. This is reasonable because systems opt-in to RBAC by using non-admin users, so installs with 'admin' users will bypass this default policy.
One new permissions will be created. This will not be associated with any specific model, either a user has it or they don't.
- ("execute_orphan_cleanup", "Can execute orphan cleanup"),
The orphan cleanup view will require this permission to execute. This view will not provide any queryset filtering as there are no orphan_cleanup views.
Related issues
Updated by bmbouter about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Sprint set to Sprint 80
Updated by bmbouter about 4 years ago
- Blocked by Issue #7448: Users or plugin writers cannot create an AccessPolicy instance that does not auto-create permissions added
Updated by rchan about 4 years ago
- Sprint deleted (
Sprint 80)
Removing from current Sprint 80. Target for Sprint 82. Can be added back to Sprint 81 if staffing allows.
Updated by bmbouter about 4 years ago
- Status changed from ASSIGNED to NEW
- Assignee deleted (
bmbouter)
Moving back to NEW, I am not actively working on this.
Updated by pulpbot almost 3 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
.