|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I'm closing this bug as "not a defect".
As I wrote in my comment, this mode of deployment isn't a conforming AD environment. For example, you won't be able to put a Windows client in EC2 that authenticates with this read-only domain controller on your DMZ.
The point of AD plugin is to reduce the amount of configuration as much as possible by maximally taking advantages of the AD environment. The proposed improvement would go the opposite direction.
I see no reasons why you cannot treat this as just another LDAP server, which Jenkins already provide a good connectivity to.