Hello CAS Developers,
I have made significant progress on an LDAP-backed TicketRegistry
(using OpenDS), and it is working very well. It is based on what I
wrote here with the modification that all tickets are replicated in
LDAP:
http://tp.its.yale.edu/pipermail/cas/2009-January/010701.html
My question now is, how is Single Sign Out implemented? More
specifically, how is it tracked inside of CAS (specifically related to
the ticket registry) so that it works? I have searched high and low in
the code and the only reference to updating a ticket is in
AbstractDistributedTicketRegistry (which I am extending just like the
Memcache and JPA registries do), and it is only called from within its
private ProxiedTicket inner class.
If you need more specifics about what I am looking for, please let me
know.
I will be more than happy to put the technical details of how Single
Sign Out works on the Single Sign Out page of the wiki, but I need to
understand it first.
Thanks!
-lucas
--
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-dev
