On Mon, Apr 4, 2022 at 11:13 AM Jon Brohauge <jonbroha...@gmail.com> wrote:

> Whenever I try to POST a job, using a Basic Authentication with the
> “username:password” base64 encoded, I get a 403.
>

Crumbs are session-specific since 2.176.2:
https://www.jenkins.io/doc/upgrade-guide/2.176/#upgrading-to-jenkins-lts-2-176-2

Either use an API token, or record the `Set-Cookie` response header and it
the same session ID with every subsequent request.


> Whenever I try to POST a job, using a Basic Authentication with the
> “username:apitoken” base64 encoded, I get a 500. The apitoken has been
> handmade just for this test.
>

The reason for the HTTP 500 is something the logs on Jenkins should tell
you. My guess is you forgot to set `Content-Type: text/xml` as documented
in `/job/whatever/api/`.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMo7PtK7WUYUD5AV%2BQr8MvdJ8fjJrJCa5%2B4dNwKedTs_a0OLxA%40mail.gmail.com.

Reply via email to