It's also used by the Acl (acls) packages by the EhCacheBackedAclCache.
It would be very easy to swap this out with another implementation of
the AclCache interface.
Ray Krueger wrote:
> Yes, it's used in core. It is the default backing for the "UserCache".
>
> On 11/6/07, Scott Battaglia <[EMA
I've created an issue and marked it for 1.0.6:
http://opensource.atlassian.com/projects/spring/browse/SEC-592
Ray Krueger wrote:
> Number 3 above is generally the pattern followed in Acegi...
>
> private StatelessTicketCache statelessTicketCache = new
> NullStatelessTicketCache();
>
> ...with a s
Yes, it's used in core. It is the default backing for the "UserCache".
On 11/6/07, Scott Battaglia <[EMAIL PROTECTED]> wrote:
> The StatelessTicketCache is only used within the CAS support for the
> purpose of simulating sessions for stateless remote access. Normal CAS
> support does not require t
The StatelessTicketCache is only used within the CAS support for the
purpose of simulating sessions for stateless remote access. Normal CAS
support does not require the StatelessTicketCache (in fact the CAS
protocol doesn't really recommend you re-use the single use tickets ;-)).
I'm okay with
Number 3 above is generally the pattern followed in Acegi...
private StatelessTicketCache statelessTicketCache = new
NullStatelessTicketCache();
...with a setter for it defining a custom implementation.
I don't think that would be a big deal to change, though I'm unsure of
it's role in the CAS s
Ben,
Do you have any objections to removing the fact that a
StatelessTicketCache is required for the CasAuthenticationProvider? Its
only needed when a remoting protocol is used and requires every
application to possibly have an unnecessary dependency on EhCache.
We have three options:
1. Just
