I'm trying to setup CAS behind an AJP proxy from HTTPD to Tomcat. That's
all fine and easy to do. The problem I'm having is that I'm trying to
change the path at the same time, and the login form isn't having any of
it by using the Tomcat path of the application. Not sure if there is a
setting I'm missing or not. Given that I'm using AJP, it should know
what the request URL is. I'm not on 2.4, so I can't modify the form URL
on the fly.
Why am I trying to do this? We currently run CAS for our institution,
which live in the Tomcat context of /cas. We were running it for another
group at effectively /cas-foo. We were proxying form /cas-foo to
/cas-foo and that works just fine.
Now we're going to run it for another institution. The plan is to run it
on the same Tomcat as our cas, so their Tomcat webapp path would need to
be /cas-bar. However, with this new one they are going to have their own
domain being fronted by HTTPD. So I would love for this to work:
https://apps.bar.edu/cas -> ajp://localhost/cas-bar
This way they can have a nice simple /cas in the URL, but it can be
deployed to the same Tomcat instance as our CAS. The current problem is
the login form has action="/cas-bar/login;jsessionid=...".
If we have to, we can do https://apps.bar.edu/cas-bar, but that is less
preferable. Is there a way to make this work with 3.5.2? Is it a bug or
a security feature?
Thanks,
Richard
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
