On Tue, May 10, 2016 at 10:53 AM, Daniel Beck <[email protected]> wrote:
> > > On 10.05.2016, at 10:13, Sorin <[email protected]> wrote: > > > > - sending a GET or PUT request with URL encoded parameters, failed > miserably .../buildWithParameters?token=MY_TOKEN&myparam=VALUE answers > dryly 403 forbidden (why forbidden?) > > The token only allows building if the authentication otherwise allows read > access to the job. > Thank you - I went to Jenkins general security settings, enabled anon users readonly access and lo, triggering builds with the GET URL works! > > - sending a POST request with payload like > json='{"parameter":[{"myparam":"VALUE"}]}' (or > Note that passing the JSON string is a hackish unsupported solution -- > this approach emulates what a web browser does, and the browser submits > whatever the "Build with Parameters" form tells him to, i.e. there's no > reasonable expectation of backwards compatibility if we ever change the > form. > I think people try these hackish solutions when they aren't shown any recommended solution. Could we (I'd gladly do it) add the above answer to the relevant Jenkins page, so nobody has to lose hours like I did? Many thanks Sorin -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAN-aYrSXaKP1Bx1ysUNPF-tfqeE6tC_WKgTpkFcUB5noxJEF7w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
