Robert Campbell edited a comment on Bug JENKINS-21583

I followed the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Disable+security and I have a workable server back in its original non-secured state. So I've lowered the priority.

But with a fresh start, modifying only the Domain Name and getting a successful Test, I Save the security configuration and get the same error and the same hosed Jenkins configuration. The relevant portion of the config.xml is as follows:

<hudson>
  <useSecurity>true</useSecurity>
  <authorizationStrategy class="hudson.security.AuthorizationStrategy$Unsecured"/>
  <securityRealm class="hudson.plugins.active_directory.ActiveDirectorySecurityRealm" plugin="[email protected]">
    <domain>mydomain.com</domain>
    <bindPassword>VkY0/D7A4NGyfaULq8auSQ==</bindPassword>
  </securityRealm>
</hudson>

I'm guessing the error comes from having a bindPassword without a Bind DN to go with it. I tried removing the bindPassword from the config.xml, but that gave me a similar error. So is there a way to configure the active-directory plugin without specifying the Bind DN/Password?

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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to