Hey guys, thanks for the input. I actually figured out what it was. I was using an old version of the ldap password expiration module that had the SSO bug (oops!). I updated that to the new version and everything is fine.
Thanks again! Kris Kristopher Borchers Web Application Developer - Content Analyst Saint Xavier University Ph. 773-298-3924 [email protected] <mailto:[email protected]> www.sxu.edu <http://www.sxu.edu> Saint Xavier University - Success with Purpose. Saint Xavier University, a Catholic institution inspired by the heritage of the Sisters of Mercy, educates men and women to search for truth, to think critically, to communicate effectively, and to serve wisely and compassionately in support of human dignity and the common good. From: Scott Battaglia [mailto:[email protected]] Sent: Monday, January 25, 2010 8:58 AM To: [email protected] Subject: Re: [cas-user] SSO not working properly SSO also depends on SSL. A non-SSL environment will not have SSO. Cheers, Scott On Mon, Jan 25, 2010 at 9:54 AM, Marvin Addison <[email protected]> wrote: > It's like the "session" isn't be handled properly. It's the session in the sense of the CAS SSO session, not a typical Web application container-managed session. I would be curious whether each authentication results in the creation of a new CASTGC cookie in your browser. Do you have a single CAS instance or multiple? What TicketRegistry are you using? M -- 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 -- 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
