[
https://issues.jenkins-ci.org/browse/JENKINS-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cervator resolved JENKINS-6206.
-------------------------------
Resolution: Fixed
Wow this ticket sure was a blast from the past, I forgot I ever filed it :-)
This went away long ago - I didn't notice exactly when, but I have a vastly
newer AD plugin as well as base Jenkins install these days
Thanks for provoking an update to this item - after finally getting my account
sorted back out (was from the java.net days) I'm now able to close this happily
:-)
> ActiveDirectory groups seem to work as global admins, but not as matrix-style
> job members
> -----------------------------------------------------------------------------------------
>
> Key: JENKINS-6206
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6206
> Project: Jenkins
> Issue Type: Bug
> Components: active-directory
> Environment: Windows 2003 Server, Hudson 1.342, AD plugin 1.16
> Reporter: Cervator
> Priority: Minor
>
> We have our Hudson configured with the AD plugin to authenticate against two
> different domains, and everything works great! No special config needed past
> installing the plugin and entering the two domains under the global config.
> However, while I can use a plain standard AD group to assign its members
> admin rights in Hudson via Manage Hudson - Configure System - Project-based
> Matrix Authorization Strategy, the same exact group won't give rights if
> assigned directly in a job using Enable project-based security.
> I can assign rights to the individual members of the group and it works fine,
> so there's a pretty easy workaround. Still, I wouldn't mind if the group
> option worked in both places, and hope it is something simple to fix :)
> If I can provide any additional troubleshooting information, please let me
> know how! I'm not very familiar with AD, so I was very happy (and a little
> surprised) when it worked this well right out of the box.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
