Crumb support with current LTS versions #429
Comments
|
We are on 2.176.3 (with an update to 2.190.1 waiting for restart) and our software using this lib to communicate with jenkins failed on the update to 2.176.3, had to disable crumb's so it work's again, but I don't like this as a permanent solution. |
|
Good estimates I have this problem activating CSRF Protection in the latest LTS version crumb = $ (curl -u "admin: admin" -s 'http://192.168.10.2:8080/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)')and then I pass it with the operation that I want to perform curl -u "admin: admin" -H "$ crumb" -X POST 'http://192.168.10.2:8080/job/ENV/build?delay=0sec'this is the way out <meta http-equiv = "Content-Type" content = "text / html; charset = utf-8" />
<title> Error 403 No valid crumb was included in the request </title>
</head>
<body> <h2> HTTP ERROR 403 </h2>
<p> Problem accessing / job / ENV / build. Reason:
<pre> No valid crumb was included in the request </pre>I would like to know what state this is or what is the new way of working with the API to launch groovy scripts Thanks in advance |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, as https://jenkins.io/doc/upgrade-guide/2.176/ tells us the upcoming / current versions of Jenkins will further increase the pressure on crumbs. We have not yet updated and are still on 2.176.1 but from colleagues I heard that their integrations (for example with Ansible) broke.
Are there plans to update this library in order to make it fit for the new enhanced crumbs ?
(I assume that your current approach is not compatible, forgive me if I'm wrong)
The text was updated successfully, but these errors were encountered: