Create a user with ADMINISTER and without RUN_SCRIPTS permission (ATH test case)

[Ullrich Hafner]

How can I configure a user in an ATH test case who can edit the Jenkins global configuration (i.e., has ADMINISTER permission), but has no RUN_SCRIPTS permission? Seems that this permission is not available in the Matrix based security.

[Stephen Connolly]

you need to turn on the separation of permissions... system property or something like that

On 13 July 2017 at 03:55, Ullrich Hafner <ullrich...@gmail.com> wrote:

How can I configure a user in an ATH test case who can edit the Jenkins global configuration (i.e., has ADMINISTER permission), but has no RUN_SCRIPTS permission?  Seems that this permission is not available in the Matrix  based security.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7D1DB319-54A5-491C-9EB2-B4F72A0D6278%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Jesse Glick]

On Thu, Jul 13, 2017 at 6:55 AM, Ullrich Hafner
<ullrich...@gmail.com> wrote:
> How can I configure a user in an ATH test case who can edit the Jenkins global configuration (i.e., has ADMINISTER permission), but has no RUN_SCRIPTS permission? Seems that this permission is not available in the Matrix based security.

No, there is no UI for such a configuration using `matrix-auth`, so
such a scenario cannot be tested using ATH.

Anyway ATH is a poor fit for tests like this. Use `JenkinsRule` +
`MockAuthorizationStrategy`.