All of the distributed ticket registries should return proxies that know to
"update" the storage whenever a method is called that changes the state.  At
least in theory they should :-)

-Scott


On Wed, Apr 15, 2009 at 11:19 PM, Lucas Rockwell <[email protected]> wrote:

> Hi Scott,
> Thanks for the response.
>
> On Apr 15, 2009, at 8:06 PM, Scott Battaglia wrote:
>
> When a service ticket is granted, the TGT internally keeps track of
> services and when you call expire() it does the callbacks.  That's the "in
> the nutshell" description :-)
>
> Its a little cludgy once you start using other ticket storage mechanisms.
> We're addressing that in CAS4.
>
>
> So, when the TGT is fetched from the ticket storage (to issue the ST) it is
> updated with the new ST info, but then the updated TGT is not saved back...?
> How does this work with the ticket registries that come with CAS, because,
> for instance, the JBossCache registry seems have enough info for the
> callbacks to work... Does the JPA registry not allow for callbacks? (Sorry,
> these may be rhetorical questions at this point.)
>
> -lucas
>
> On Wed, Apr 15, 2009 at 12:34 PM, Lucas Rockwell <[email protected]> wrote:
>
>> 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
>>
>
>  --
> 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
>
>
>
> --
> 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
>
>

-- 
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

Reply via email to