Sorry for the delayed response on this. I'm actually looking at
revisiting not only the Acegi CAS clients, but also the CAS clients in
general.
I've posted some initial work on re-working the underlying CAS clients
(and updating the Acegi code to reflect the new CAS code).
That code can be
nt: Friday, April 21, 2006 6:24 PM
To: acegisecurity-developer@lists.sourceforge.net
Subject: Re: [Acegisecurity-developer] Re: CAS configuration
Marc-Antoine Garrigue wrote:
I see 3 solutions :
I will refer this one to Scott, as he maintains the CAS
integration these days. Scott, your thoughts?
You don't mean McCrory, do you? I'm just involved with Siteminder.
Scott (M)
> -Original Message-
> From: Ben Alex [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 21, 2006 6:24 PM
> To: acegisecurity-developer@lists.sourceforge.net
> Subject: Re: [Acegise
Marc-Antoine Garrigue wrote:
I see 3 solutions :
I will refer this one to Scott, as he maintains the CAS integration
these days. Scott, your thoughts?
Cheers
Ben
---
Using Tomcat but need to do more? Need to support web services, securit
All,
I am setting up a CAS instance for 300 000 users, and a first
perimeter of 150 applications.
In this context, I use the identity forwarding facility provided by
CAS (Proxy Ticket) to build personalized/authenticated web service
aggregation in a corporate portal.
I'm also experiencing some iss
On 3/16/06, Baz <[EMAIL PROTECTED]> wrote:
> Looking at this, and the way that the 'Filter' classes aren't really
> (the lifecycle methods arent used, and they're all marked 'do not use
> directly') shouldn't all of these implement something like:
must...think...before...hitting...send
ok cle