Yep, you were right! I was thinking it was CAS because SSL was working fine with our previous Tomcat config. Only when we added CAS to the mix did it break. However, editing context.xml to set cookies="true" and disableURLRewriting="true" as described in your link has fixed the problem.
Thanks you very much! On Tue, Apr 16, 2013 at 1:49 PM, Ohsie, David <[email protected]> wrote: > This is really a tomcat question, not a CAS question and it may depend on > your version of tomcat. Here is a possible starting point:**** > > ** ** > > http://fralef.org/tomcat-disable-jsessionid-in-url.html**** > > ** ** > > David Ohsie**** > > Software Architect**** > > EMC Corporation**** > > ** ** > > ** ** > > *From:* Shaunn Barron [mailto:[email protected]] > *Sent:* Tuesday, April 16, 2013 10:33 AM > *To:* [email protected] > *Subject:* [cas-user] jsessionid cookie not being set**** > > ** ** > > Hello all,**** > > ** ** > > I'm having an issue getting CAS/Tomcat to set the jsessionid cookie over > ssl. Everything works fine when running locally from Eclipse...but when I > deploy to our dev environment, we end up with the jsessionid in the url > rather than in a cookie.**** > > ** ** > > Any ideas on this?**** > > ** ** > > Thanks,**** > > Shaunn**** > > -- > 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**** > > -- Shaunn Barron http://www.shaunnbarron.com -- 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
