Active Directory authentication + Build agents

[Daniel Becroft]

Hopefully this is a quick question.

We are currently moving to Active Directory authentication for Jenkins (as we can't get emails to send to our developers unless Jenkins knows about them now). Our plan is to create a group in AD (JenkinsUsers), put everyone into that group, and then give the permissions to that group.

Our build slaves are (mostly) configured to run as Windows Services under generic accounts. Do the account that those slaves run under need to be included in that group? Does that account get authenticated/authorized in any way? Or are the agent user accounts a separate area.

Cheers,

Daniel B.

[Ivo Bellin Salarin]

Are you using the AD plugin?
https://wiki.jenkins.io/plugins/servlet/mobile?contentId=7536642#content/view/7536642

What are you willing to do with the build accounts?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAJM0iSR7OuhO-LK8swTkaoUbA_oR9uMw0u0oACg5j7XCUyem2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Beck]

> On 11. Aug 2017, at 07:35, Daniel Becroft <djcbe...@gmail.com> wrote:
>
> Our build slaves are (mostly) configured to run as Windows Services under generic accounts. Do the account that those slaves run under need to be included in that group? Does that account get authenticated/authorized in any way? Or are the agent user accounts a separate area.
>

Whatever local account a node runs as determines what you can do with it (For example which files to access/modify), but otherwise it doesn't matter for Jenkins. User authentication is unrelated.