Hello,
We are using a Jenkins Master and Slave (both Linux) type setup. Recently 
upgraded to LTS version and for some reason Slaves connects to Master only 
when Anonymous is given Admin privileges.
I have read the posts about providing Anonymous slave connect privileges 
but I receive a 403 request forbidden error when I try that.
The only way around for this is to provide Anonymous Admin privileges 
(which is risky) save it and then go back to Manage Jenkins > Configure 
Security > Remove Anonymous Admin > Add Slave connect privileges.
The issue in doing this workaround is, I get the same 403 error when slave 
restarts until I give Anonymous admin privileges.
I have tried laying down a new slave.jar that didn’t help.
We are using a LDAP Bind account, is there an easy fix to this 403 issue 
without having to enter the bind password again (which we recently did 
after the Jenkins upgrade)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" 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/d/optout.

Reply via email to