Seeking clarification on application/CAS logout behavior

[Andrew Feller]

James,

As Robert mentioned, the SSOut feature has been available since CAS 3.1.0,
however there was an important bug fix for it at 3.1.1.  Make sure you are
using a version of 3.1.1 or higher.  Also, you need to update your CAS
clients to the JA-SIG Java CAS client 3.1 as the SSOut feature requires some
work on the client side.  You will need to update the JAR and add a new
filter and listener.  For more information, please checkout its wiki page:

http://www.ja-sig.org/wiki/display/CASC/CAS+Client+for+Java+3.1

HTH,
A-


On 12/14/08 3:51 PM, "Robert Oschwald" <robertoschwald at yahoo.de> wrote:

> James,
> 
> in fact, CAS not only supports Single Sign On, but also Single Sign
> Out since Version 3.1.
> Please see http://www.ja-sig.org/wiki/display/CASUM/Single+Sign+Out
> for details.
> 
> 
> Robert
> 
> Am 14.12.2008 um 21:58 schrieb James Stoll:
> 
>> It seems to me, as someone relatively new to this process, that
>> ideally,
>> upon application logout, CAS would examine whether or not the user
>> still
>> has an active session in any 'registered' applications (perhaps
>> through
>> examination of a browser cookie?), and if the user is logging out of
>> the
>> last active application session, then the CAS session would be
>> terminated, but if there were any other 'registered' application
>> sessions still active, then the CAS logout would not occur. (just the
>> logout of the app from which the user hit the 'logout' link.)
> 
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas