|
||||||||
|
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.

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:
I'm guessing the error comes from having a bindPassword without a Bind DN to go with it.