CAS sets its cookie path to whatever the first request context path it receives is. You should be able to see from the cookie returned what path is being set.
Cheers, Scott On Tue, Nov 23, 2010 at 6:43 AM, Thomas FRANCART < [email protected]> wrote: > Hi Scott > > Thanks for your reply. > Can you confirm that, if we access CAS at the url > http://myserver.com/node01/cas, the cookie path should be /node01/cas > instead of /cas ? > We have setup our cas clients through JNDI, using the public URLs of CAS, > this way : > > java:cas/serverName = http://myserver.com/node01 > java:cas/AuthenticationFilter/casServerLoginUrl = > http://myserver.com/node01/cas/login > java:cas/Cas20ProxyReceivingTicketValidationFilter/casServerUrlPrefix = > http://myserver.com/node01/cas > > Could the problem originate from these parameters ? > > Thomas > > > On Mon, Nov 22, 2010 at 20:15, Scott Battaglia > <[email protected]>wrote: > >> CAS sets up its path based on the Request Context Path by default. >> >> Its all in this: >> >> https://source.jasig.org/cas3/tags/cas-server-3.4.3.1/cas-server-core/src/main/java/org/jasig/cas/web/flow/InitialFlowSetupAction.java >> >> Might be messing with you? >> >> >> >> On Mon, Nov 22, 2010 at 12:05 PM, Thomas FRANCART < >> [email protected]> wrote: >> >>> Hi all >>> >>> I have a CAS server along with multiple applications integrated with it >>> in one application server; all of that is behind an Apache server configured >>> as a reverse proxy, with the following lines >>> >>> ProxyPass /node00 http://localhost:8080 >>> ProxyPassReverse /node00 http://localhost:8080 >>> >>> From outside of the server, the URLs are : >>> >>> http://myserver.com/node00/cas for the CAS server >>> http://myserver.com/node00/appA for application A >>> http://myserver.com/node00/appB for application B >>> >>> Login works when I log into appA. However, when switching to the appB, >>> the CAS server asks me to login again, as if it hadn't detected that I was >>> already logged. This works when I access the applications directly from >>> http://localhost:8080/appA or .../appB. I see that CAS puts a TCKT >>> cookie with path "/cas" in my browser. Shouldn't this cookie path be >>> "/node01/cas" for it to work properly ? if yes, how to change that ? >>> >>> Thanks for your help >>> Thomas >>> >>> -- >>> *Thomas Francart* >>> *CTO** - Mondeca* >>> 3, cité Nollez 75018 Paris France >>> Tel. +33 (0)1 44 92 35 04 - fax +33 (0)1 44 92 02 59 >>> Web: www.mondeca.com >>> Blog : Leçons de choses <http://mondeca.wordpress.com> >>> >>> <http://www.online-information.co.uk/promo/online2010/ex25175> >>> >>> >>> -- >>> 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 >> >> > > > -- > *Thomas Francart* > *CTO** - Mondeca* > 3, cité Nollez 75018 Paris France > Tel. +33 (0)1 44 92 35 04 - fax +33 (0)1 44 92 02 59 > Web: www.mondeca.com > Blog : Leçons de choses <http://mondeca.wordpress.com> > > <http://www.online-information.co.uk/promo/online2010/ex25175> > > > -- > 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
