> I guess what I was really looking for is a way of making sure the handlers > get run again.
I can say from experience that you can do just about anything you can imagine with Spring Webflow. We don't have any documentation on the makeup of the CAS login webflow because it's basically self-documenting. (Assuming the reader has general SWF background.) > Is there a way of having those run during authentication, AND during any > redirection to the service, AND store information in the session for later > retrieval? Your mention of session is concerning. Storing data in the SWF flow scope is synonymous with session storage (since it uses that under the hood), but it's important that you understand the scope of the login webflow is relatively short. It begins when the user first hits the login form, and in the case of successful authentication ends with the generation of a service ticket. The flow state effectively evaporates at that point. More generally, even if you were to store data directly in the session, it would be unreliable at best since interaction with CAS is sporadic and you'd likely have session timeouts where your session data on the CAS server is lost. So if you mean session to be the lifetime of a CAS SSO session, then both flow storage and underlying session storage is unsuitable for your needs. At that point your integration scenario becomes much more complex since you'd need to store your data into a durable store like that used by TicketRegistry, for example. 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
