Tim,
You should extend the UsernamePasswordCredentials to accept your new
property.  Then create a MetaDataPopulator to take that property and dump it
into the attributes for the Authentication object.  Configure that all using
the Spring magic ;-)  And then your custom ticket expiration policy will
have the value.

-Scott

On Tue, May 27, 2008 at 5:13 PM, Tim Mc Laughlin <[EMAIL PROTECTED]>
wrote:

> OK, spoke too soon.
>
> The difference between what I'm trying to do and what Trenton Adams wanted
> is that I'd
> like to be able to have the user select which role they're in, via a
> checkbox on the login
> form.
>
> I've located where and how to implement a new TicketExpirationPolicy, but
> I'm not sure how
> to let the value of the checkbox flow through to that code.  Is that
> possible without
> changing core code?  I'd like to stick to recognized extension points only.
>
> Thanks,
> Tim
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Tim Mc
> Laughlin
> Sent: Tuesday, May 27, 2008 11:55 AM
> To: [email protected]
> Subject: "Lab" timeout different than "Office" timeout?
>
> I am almost sure I've seen this question fly across the list, but none of
> my queries have
> been right to find it in the archives, so apologies in advance.
>
> I've been asked if we can implement variable timeouts based on role, the
> most
> straightfoward of which will be a checkbox on the login form that can be
> checked if you're
> on a "Lab" or "Public" computer.  Checking this would result in a shorter
> CAS timeout than
> an "Office" or "Private" computer.
>
> Can someone point me in the right direction?
>
> Thanks,
> Tim
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>


-- 
-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to