CAS plugin with Jenkins 2

[c...@nine.ch]

I'm having troubles with the CAS plugin.

The plugin will redirect me to my CAS server. When I authenticate on the CAS server, I get redirected to jenkins.

Now I should be logged in, but I'm not.

I get redirected to https://jenkins01/login?service=https%3A%2F%2Fjenkins01%2FsecurityRealm%2FfinishLogin

... which seems like Jenkins protects the finishLogin page.

Does anyone has the CAS plugin (CAS 2.0 protocol) working with Jenkins >2.9? (I tested with 2.9 and 2.17)

Plus it would be helpful if someone could guide me to what Loggers on which Levels I should listen to. Now I either get noise or nothing.

~Chris

[Matthew...@diamond.ac.uk]

I use the CAS plugin v1.2.0 using CAS protocol 2.0, and Jenkins 2.17.

We have not had any CAS-related issues (never, I think).

However, we run our Jenkins on http (not https), using the embedded web server (Jetty?), and not in a container like Tomcat.

 

Did you have this working, and then it broke, or are you trying to set it up for the first time?

 

Matthew

--

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 

[c...@nine.ch]

Never mind. I messed up with the Apache reverse proxy, which terminates my TLS. All redirects from the CAS plugin to the CAS server were re-written by Apache http to point back to itself.

In any case, thanks for confirming that the setup Jenkins 2.17 and CAS 2.0 should work!

~Chris