"The current problem is the login form has
action="/cas-bar/login;jsessionid=..."."
If your proxy is getting hung up on the jsessionid in the url in its path,
and you're running Tomcat 7 or Tomcat 8, you can modify web.xml in the
cas-bar/WEB-INF directory by adding a tracking-mode tag:
<session-config>
<!-- Default to 5 minute session timeouts -->
<session-timeout>5</session-timeout>
<tracking-mode>COOKIE</tracking-mode>
</session-config>
Setting to COOKIE removes the jsessionid from the URL.
Ken
On Fri, Feb 21, 2014 at 10:54 AM, Alberto Cabello Sánchez
<[email protected]>wrote:
> On Thu, 20 Feb 2014 10:32:45 -0600
> Richard Frovarp <[email protected]> wrote:
>
> > 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
>
> You can possibly achieve it through a Rewrite (or Redirect, I can't
> remember)
> in front of the AJP request?
>
> > 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=...".
>
>
> --
> Alberto Cabello Sánchez <[email protected]>
>
> --
> 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
>
>
--
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
