> > It did lead me to wonder about the "gateway=true" parameter and whether > there is a way to somehow use this.
[DO] That setting will ensure that the user doesn’t get a login screen. You will get a ticket if there is an SSO session established at CAS and not if there isn't. > > I also came across mod_auth_cas and wondered if this could somehow > mitigate my problem but could find a clear explanation of what it was for and > how it worked architecturely. [DO] mod_auth_cas is CAS client (where client = agent in CAS terminology) that runs as an apache module. It is an alternative to the other cas clients such as the Java Cas Client, the spring CAS client and the php cas client. It won't solve this issue. The first thing you really need to decide is what behavior you want. If you want the client's SSO session to be extended by the activity of any CAS protected application, then you need to do something on the application to keep the session alive. CAS has no idea what accesses are happening on the application and can't extend its session automatically based on application/browser activity. > -- > 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
smime.p7s
Description: S/MIME cryptographic signature
