On Wed, May 9, 2012 at 4:48 AM, Odilo Oehmichen
<odilo.oehmic...@gmail.com> wrote:
> Hi,
>
> CAS 3.5 will support an EhCache solution for the ticketregistry (see [1]).
> That's nice.
>
> I have two questions concerning the implementation:
>
> 1. The EhcacheTicketRegistry uses 2 different caches: one for the Ticket
> Granting Tickets and one for the Service Tickets. - The
> CentralAuthenticationServiceImpl has that differentiation too, but on the
> TicketRegistry-level.
> Why did you decide to provide it in the EhcacheTicketRegistry?
Two caches are there to have different cache settings for TGT vs ST.
It could have been implemented differently.
> So the differentiation in the CentralAuthenticationServiceImpl is obsolete?
In practice, yes. I don't know of any implementation taking advantage
of the CASImpl notion of separate registries. In
applicationContext.xml you'll only find a setter for ticketRegistry on
centralAuthenticationService. Also in CASImp you'll find
public void setTicketRegistry(final TicketRegistry ticketRegistry) {
this.ticketRegistry = ticketRegistry;
if (this.serviceTicketRegistry == null) {
this.serviceTicketRegistry = ticketRegistry;
}
}
which at first glance looks like a possible race condition if
serviceTicketRegistry was also defined in the bean config.
>
> 2. There is an overlap between the ExpirationPolicy configured for a ticket
> and the
> eviction policy (aka timeToLive) configured with the EhCacheFactoryBean. Is
> that right?
Yes. These settings should match up.
Best,
Bill
>
> Thanks
> Odilo
>
> [1] https://wiki.jasig.org/display/CASUM/EhcacheTicketRegistry
>
> --
> You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
