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
Am
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
