Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

authorization for "Adhoc" jobs needs explicit support in aclpolicy

#61

aclpolicy should have explicit way to authorize "adhoc" commands.

Currently:

  • If you try to run an adhoc job, it actually creates a transient job named "Temporary_Job" and with group "adhoc" (these are just placeholder non-null property values for the transient instance), so in order to authorize a user/group to run adhoc commands you need to set aclpolicy to allow a job with that name/group, but this is not very clean.
  • If you view an Execution page, the option re-run the execution is only shown when authorization allows a job named "adhoc" and with a group named "adhoc" -- this is also not very clean and is inconsistent with the previous item.

suggest that we add something like: <job adhoc="true/false"> to the aclpolicy

Reported by Greg Schueler · November 3rd, 2010 @ 10:21 AM

State: duplicate
Milestone: Rundeck 1.4
Assigned to: Greg Schueler Greg Schueler

Activity

  1. Alex-SF
    Alex-SF
    • Milestone set to Rundeck 1.1
    • Milestone order changed from 12 to 0

    November 24th, 2010 @ 08:39 AM

  2. Alex-SF
    Alex-SF
    • Milestone changed from Rundeck 1.1 to Rundeck 1.2
    • Milestone order changed from 13 to 0

    December 29th, 2010 @ 05:53 PM

  3. Alex-SF
    Alex-SF
    • Milestone cleared.
    • Milestone order changed from 1 to 0

    February 15th, 2011 @ 11:31 AM

  4. Greg Schueler
    Greg Schueler
    • Assigned user set to Greg Schueler
    • Milestone set to Rundeck 1.4
    • Milestone order changed from 36 to 0

    September 7th, 2011 @ 11:28 AM

  5. Greg Schueler

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.