I have a strange problem. My user on jenkins (1.517) has an API token.
A REST request (via POST) like this: http://angelo:apiToken@jenkins-server:8080/safeRestart?token=weirdtokenstring only works if "angelo" is already logged on on Jenkins via the web interface. (Yes, my script which has no cookie or any awareness about the browsers session works.) So, what now? Do I need to write a lengthy script that loggs on to the server first before I send the above REST request? What is the point of the apiToken if it only works if I'm already authenticated? If I'm authenticated I simply can use this URL http://jenkins-server:8080/safeRestart. Is this a bug or intended behaviour? (Also: I got the suggestion for the URL I use from here: https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients respectively from my Jenkins instance /api url. However as I'm supposed to sent a POST, I wonder if it is correct to send the parameters in the URL encoded) Any hints welcome :D Thanx, Angelo -- 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.
