Jenkins has a servlet filter [1] that last time I checked accepts http basic
auth. But I’m not sure how/if this works when delegating to the servlet
container, you’d probably need to authenticate the way the container dictates
in that case.
[1]
https://github.com/jenkinsci/jenkins/blob/master/
Robert is correct - when delegating you are entirely subject to
authentication against the container. Jenkins handles no part of
authentication in this situation. It only handles authorization via
roles/groups which you sometimes have to tell the container to map. For
example, you have a user scott
Thank you Robert and Ben for your tips.
This is the closest I've been able to come to reproducing the form-based
authentication captured with wireshark.
curl -v -c cookies.txt http://localhost:8080/jenkins/
200 OK
curl -v -c cookies.txt -b cookies.txt
http://localhost:8080/jenkins/loginEntry
A good test to see if jenkins properly recognizes the container role is if
it does not offer a delete option next to the role in the matrix security
config.
Also, looks like you're trying form based and trying to get curl to store
the session cookie. You might try basic auth instead.
Out of curio
If login through gui works OK then try token based [1] and see if that
works.
Other than that I am stumped.
[1]
https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients
On Jun 12, 2014 12:53 PM, "Ben Castellucci" wrote:
> A good test to see if jenkins properly recognizes the
Ha ha ha ok, sorry, you already tried that link I sent.
(Sigh)
Maybe try again after you confirm success through the gui?
When I do this it's against jenkins deployed to weblogic. I use a
deployment plan to transform web.xml to add CLIENT-CERT to auth config and
then configure the security realm
