IIRC this was fallout from fixing a critical security issue
On 12 February 2013 16:21, Les Mikesell <[email protected]> wrote: > On Tue, Feb 12, 2013 at 9:37 AM, Fisher, Allen <[email protected]> > wrote: > > I did notice something interesting. If I launch via the website, the > slaves > > will connect, until I install the service. After that, they don’t > connect. > > If it works when you are authenticated in the browser before > launching, but not as a service it is because the system changed to > require slaves to authenticate via jnlp but it seems to be mostly > broken. I changed mine to start via ssh (linux) and 'let jenkins > control this windows slave" on the windows systems where that worked. > Not sure what to do about the windows 2008 systems where none of that > works. > > If you are on a private firewalled LAN, you might be OK with allowing > anonymous read and slave connect in your main authorization matrix to > restore the old behavior. > > By the way - was this change documented somewhere for the LTS 1.480.2 > release?. I had seen the problem mentioned for 1.49x versions but > wasn't expecting it in 1.480.2. - and I thought the point of the LTS > line was to avoid surprises. > > -- > Les Mikesell > [email protected] > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
