Bug #4450
Tasks API is not authorized
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Description
There should be permissions defined around shouwing the tasks.
Waiting till the new foreman permissions system is in.
Related issues
Associated revisions
History
#1
Updated by Walden Raines about 8 years ago
- Blocks Feature #5217: As a user, I should have CRUD permissions for all entities that are exposed to me. added
#2
Updated by Walden Raines about 8 years ago
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1112234
#3
Updated by Eric Helms almost 8 years ago
- Blocks deleted (Feature #5217: As a user, I should have CRUD permissions for all entities that are exposed to me.)
#4
Updated by Ivan Necas almost 8 years ago
- Blocks Feature #7514: add foreman tasks into core added
#5
Updated by Ivan Necas almost 8 years ago
- Blocks deleted (Feature #7514: add foreman tasks into core)
#6
Updated by Ivan Necas almost 8 years ago
- Blocks Feature #7514: add foreman tasks into core added
#7
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2060 added
#8
Updated by Ivan Necas over 7 years ago
- Status changed from Ready For Testing to Closed
Fixes #4450 - authorize the tasks
There are two permissions: view_foreman_tasks for viewing and
edit_foreman_tasks for controlling them.
Two default roles are pre-seeded: Tasks Reader and Tasks Manager. Also
the Anonymous role is added a permission to see user's own tasks, to
prevent the awkward moment when a user triggers a task and can't see
the progress or status.