We have a CAS app that is using the .Net Client and we are getting intermittent SSO. It seems to work fine for about 30 seconds then disappears. Reclicking on the login button immediately starts the SSO again ( no login page ) so I know the cookie is good. I'm trying to figure out if this is a caching issue or a client issue.
When a user goes to a new protected page, should there be a CAS log entry ( running DEBUG mode) for checking the cookie? Does the client handle this? thanks Jonathan Bricker ExactTarget Senior Software Engineer Office | 317.524.2789 Cell | 317.435.0763 Email | [email protected]<mailto:[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
