CAS w/ ACEGI

[Scott Battaglia]

I can't add it to the AuthenticationHandler itself, but I can create a new
Interface called NamedAuthenticationHandler that adds the parameter (and
then make it an optional configurable property on all default handlers.

We can't change the AuthenticationHandler interface itself as that's pretty
much the one everyone writes against.

-Scott

On Tue, Mar 18, 2008 at 2:53 PM, Larry Symms <lsymms at gmail.com> wrote:

> In that case would it also make sense to put in a name property on the
> AuthenticationHandlers to differentiate handlers that use the same impl
> (e.g. 2 ldap directories), or would you just add the handler object as a
> property to the Authentication object and have the MetaDataPopulator use
> the properties of the handler to differentiate it (e.g. analyze the
> context source urls to determine which server successfully authenticated
> the credentials)?  If it were up to me I'd just tack on an optional name
> property to the AuthenticationHandler interface.
>
> - Larry
>
> Scott Battaglia wrote:
> > My mistake on that one (I think I got my interfaces mixed up).   If
> > you submit a JIRA issue I'll have the AuthenticationManager populate
> > the attribute on the Authentication object by default.  This would
> > make it to 3.2.1 which hopefully should come out as an RC1 tomorrow.
> >
> > -Scott
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>



-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080318/468c7435/attachment.html