Hi, In fact, the CASTGC cookie is available for a specific domain (even shared with other applications) but also on a specific path. This ensures the security : even with no subdomain for your CAS server, the CASTGC cookie is only sent and received to/from the CAS server. Best regards, Jérôme
2013/8/6 Whittaker, Geoffrey <[email protected]> > Greetings,**** > > ** ** > > I’m continuing to work on setting up my clustered CAS solution and I’m > wondering what others have done about setting the cookie domain. **** > > ** ** > > Did you proxy your load balancers in addition to load balancing them? If > so, were you able to set the p:cookieDomain property to the proxy url? ** > ** > > ** ** > > For instance, if the users accessed CAS at cas.mydomain.com could I just > use: p:cookieDomain = “cas.mydomain.com” **** > > ** ** > > I don’t have a subdomain for the CAS servers at the moment, and the idea > of opening it up to my entire domain strikes me as a non-starter. **** > > ** ** > > Geoff **** > > -- > 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
