Yes by logging out of service1 we are ending our sso session. I will look into what I can do to 'capture' that LogoutRequest message.
Thanks. James James Bodine Manager, Web Services & Middleware Fort Lewis College - Information Technology 970-247-7304 [email protected] -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Monday, October 24, 2011 7:29 AM To: [email protected] Subject: Re: [cas-user] Unique Logout Procedure I want to make it clear that there is absolutely no solution to this problem without ending the CAS SSO session. If you simply end service1's session by logging out locally, CAS is entirely uninvolved in that scenario and can't help you. I'll assume that you mean to logout of CAS upon ending service1's session > Unfortunately we don't have the service in question using a cas > client. The application "Banner Self Service" is using older special > code to allow it to interact with cas. That's really not an issue. David's suggestion is a specific sketch of a more general strategy. The CAS server sends all services a LogoutRequest message when the SSO session ends, so you could leverage that message as an event to trigger the DB procedure call you need. So the pub/sub model Dmitriy mentioned is possible, even if it requires writing your own code to catch the message and act accordingly. 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
