-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
1.4.0
-
False
-
-
False
-
-
-
Critical
Description of the problem:
A recent change seems to have caused the rbac orchestrator use policy to no longer function, and the update policy works in its place.
Here is an example explaining the issue, using the csv file method.
The documentation states that the below policy entries could be applied to a user to give them read/write access to orchestrator workflows. However with some recent change the user is only able to read - the use does not appear to do anything.
p, role:default/workflowReadwrite, orchestrator.workflow, read, allow p, role:default/workflowReadwrite, orchestrator.workflow.use, use, allow
However with the update policy verb the user is able to execute an orchestrator workflow.
p, role:default/workflowReadwrite, orchestrator.workflow, read, allow p, role:default/workflowReadwrite, orchestrator.workflow.use, use, allow p, role:default/workflowReadwrite, orchestrator.workflow.use, update, allow
I tried the update verb because it now shows as an option in the rbac portion of the ui for orchestrator.
How reproducible:
Steps to reproduce:
1.
2.
3.
Actual results:
Expected results:
- relates to
-
FLPATH-1562 Finer Grained Permission on Workflows
-
- Closed
-