OK, so I should have been paying attention to all those SSH emails..... I just enabled LDAP authentication on my Jenkins server today allowing anyone logged in to do anything and I discovered that my small use of jenkins-cli now fails:
# # set the build display name # C:\Program Files (x86)\Jenkins\jobs\Set-Build-Display-Name\workspace>java -jar \Jenkins\jenkins-cli.jar -s http://JenkinsServer.xxxxxxx.net:8082/ set-build-display-name Debug-xxxxxx-Build 190 Mainline-Debug-x.190 hudson.security.AccessDeniedException2: anonymous is missing the Run/Update permission as it happens, the job, Set-Build-Display-Name, runs on the Jenkins server. From the CLI help, the only way to make this work now is to provide an SSH private key. But all my systems are Windows (server and slaves). The reason to enable LDAP authentication was simply to track who is doing what, no real need for access restrictions. Is my only way of getting this job to work to install an SSH server and client on the same machine and create an SSH key? Dick Ginga, Informatics R&D PerkinElmer Inc. | For the Better HUMAN HEALTH | ENVIRONMENTAL HEALTH 940 Winter Street, Waltham MA 02451 dick.gi...@perkinelmer.com<mailto:ed.cof...@perkinelmer.com> Mobile - 508-847-1434 Office - 781-663-6947 -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
