[cas-dev] CAS-452

[March, Andres]

On second thought, was the intention that we modify the authentication
to carry that info?  And then we can extract it from the auth in the
expiration policy?

 

- Andres

________________________________

From: cas-dev-bounces at tp.its.yale.edu
[mailto:cas-dev-bounces at tp.its.yale.edu] On Behalf Of March, Andres
Sent: Tuesday, February 20, 2007 1:32 PM
To: Mailing list for CAS developers
Subject: [cas-dev] CAS-452

 

I'm not sure how this resolution addresses the use case that I cited in
the issue.  We need to know the credentials in the TicketGenerator in
order to create a ticket that can be recognized by the expiration policy
as short-lived or long-lived.

 

  

Andres March

Platform - Application Engineering

Sony Online Entertainment

desk: 858.577.3373

cell:   619.519.1519

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20070220/578c9333/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 103 bytes
Desc: image004.gif
Url : http://tp.its.yale.edu/pipermail/cas-dev/attachments/20070220/578c9333/attachment-0003.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 73 bytes
Desc: image005.gif
Url : http://tp.its.yale.edu/pipermail/cas-dev/attachments/20070220/578c9333/attachment-0004.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 73 bytes
Desc: image006.gif
Url : http://tp.its.yale.edu/pipermail/cas-dev/attachments/20070220/578c9333/attachment-0005.gif