"Create and Run" is not limited by lack of workflow_execute
Reported by Moses Lei | September 6th, 2011 @ 12:36 AM | in Rundeck 1.4 (closed)
If you have the permission workflow_create but not workflow_run, RunDeck will allow you to "Create and Run" a job. It will execute, but afterwards if you try to find it again in the job list, it (correctly) prevents you from executing it at that point.
RunDeck should not allow "Create and Run" for users with workflow_create but not workflow_execute.
Comments and changes to this ticket
-
-
Greg Schueler September 7th, 2011 @ 11:37 AM
- State changed from “new” to “open”
- Assigned user set to “Greg Schueler”
will be fixed by #429
-
Greg Schueler September 9th, 2011 @ 04:19 PM
- State changed from “open” to “needs_verification”
verify fix provided by new aclpolicy support
-
Greg Schueler September 14th, 2011 @ 11:40 AM
- State changed from “needs_verification” to “resolved”
verified:
authorization:
* resource kind 'job' allowed 'create' * job group "test2.*" denied 'run'In the job form I created a job with group "test2/blah" , and clicked Create and Run. It created the job but showed error message that user was not authorized to run the job.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Greg Schueler