Great!  I have created the JIRA:http://www.ja-sig.org/issues/browse/CASC-34

-rg

On Jan 25, 2008 2:28 PM, Scott Battaglia <[EMAIL PROTECTED]> wrote:

> Adding a template method sounds relatively reasonable.  If you can create
> a JIRA issue to track it that would be great.  I'll also probably look into
> whether it makes sense to add one for failure too.
>
> -Scott
>
>
> On Jan 25, 2008 2:19 PM, rg <[EMAIL PROTECTED]> wrote:
>
> > I was afraid you were going to ask that question  ;)
> > Basically it's to deal with a scenario I mentioned in a prior email. See
> > question #1 here:
> > http://article.gmane.org/gmane.comp.java.jasig.cas.user/4230
> >
> > How I am dealing with this scenario, is I created my
> > own ExpirationPolicy which looks in a database for the last accessed time
> > for the users ticket grating ticket OR service ticket.  When the user makes
> > an http request to a service webapp, an internal web service call will be
> > made to update this "last accessed time" in the database.  What that means
> > is I need to hold onto the service ticket IDs in the http session for each
> > service.
> >
> > The problem I have is finding the appropriate place in the lifecycle of
> > the service ticket validation http request to put the service ticket ID in
> > the http session.  This is what I want to do right after the ticket is
> > validated.  And now that I think about it a little more, the template method
> > would need to be something like:
> > onServiceTicketSuccess(ServletRequest, ServletResponse, Assertion)
> >
> > I'm guessing you are going to have a negative reaction to what I just
> > described.  But know that I have control over the CAS webapp, and every
> > single webapp that uses CAS for authentication.  This is a closed system
> > with only my webapps.
> >
> > -rg
> >
> >
> >
> > On Jan 25, 2008 11:39 AM, Scott Battaglia <[EMAIL PROTECTED]>
> > wrote:
> >
> > > rg,
> > >
> > > What's your use case for the functionality that needs to happen after
> > > a successful service ticket validation?  This way we can figure out the 
> > > best
> > > way to make the library extendable.
> > >
> > > -Scott
> > >
> > >
> > > On Jan 25, 2008 9:55 AM, rg <[EMAIL PROTECTED]> wrote:
> > >
> > > > I have been using the 3.1 RC1 client for a few days in the prototype
> > > > I'm building.  So my perspective of the release client is limited, but, 
> > > > so
> > > > far I haven't seen any bugs.
> > > > One change that i would like to be considered is to
> > > > change Cas20ProxyReceivingTicketValidationFilter to NOT be marked 
> > > > final, and
> > > > to have a new template method onServiceTicketSuccess() declared
> > > > in AbstractTicketValidationFilter and called in doFilter() after
> > > > this.ticketValidator.validate().  This way I can
> > > > extend Cas20ProxyReceivingTicketValidationFilter and
> > > > override onServiceTicketSuccess().
> > > >
> > > > I understand the goal to keep certain things final, but, all i want
> > > > to do is add some code on successful service ticket validation, and I 
> > > > don't
> > > > see any way to do it currently.
> > > >
> > > > thanks,
> > > > -rg
> > > >
> > > >
> > > >
> > > > On Jan 24, 2008 10:18 AM, Scott Battaglia <[EMAIL PROTECTED]>
> > > > wrote:
> > > >
> > > > > It can be found here:
> > > > >
> > > > > http://www.ja-sig.org/downloads/cas-clients/cas-client-3.1-RC1-release.zip
> > > > >
> > > > > Documentation can be found here:
> > > > > http://www.ja-sig.org/wiki/display/CASC/CAS+Client+for+Java+3.1
> > > > >
> > > > > If you can try it out and give us any feedback that would be
> > > > > great.  We're looking to do a release soon so we can incorporate it 
> > > > > into the
> > > > > next version of Acegi.
> > > > >
> > > > > -Scott
> > > > >
> > > > >
> > > > > On Jan 24, 2008 4:11 AM, Marat Radchenko <
> > > > > [EMAIL PROTECTED]> wrote:
> > > > >
> > > > > > Where I can download it?
> > > > > >
> > > > > > 2008/1/23, Scott Battaglia <[EMAIL PROTECTED]>:
> > > > > > > Folks--
> > > > > > >
> > > > > > > We want to get ready to do the CAS 3.1 client release for Java
> > > > > > (so we can
> > > > > > > start working on 3.1.1).  I've done some testing of it
> > > > > > locally.  Has anyone
> > > > > > > else tested it that can say it works well?
> > > > > > >
> > > > > > > Thanks
> > > > > > > -Scott
> > > > > > >
> > > > > > > --
> > > > > > > -Scott Battaglia
> > > > > > > LinkedIn: http://www.linkedin.com/in/scottbattaglia
> > > > > > > _______________________________________________
> > > > > > > Yale CAS mailing list
> > > > > > > [email protected]
> > > > > > > http://tp.its.yale.edu/mailman/listinfo/cas
> > > > > > >
> > > > > > >
> > > > > > _______________________________________________
> > > > > > Yale CAS mailing list
> > > > > > [email protected]
> > > > > > http://tp.its.yale.edu/mailman/listinfo/cas
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > -Scott Battaglia
> > > > >
> > > > > LinkedIn: http://www.linkedin.com/in/scottbattaglia
> > > > >
> > > > > _______________________________________________
> > > > > Yale CAS mailing list
> > > > > [email protected]
> > > > > http://tp.its.yale.edu/mailman/listinfo/cas
> > > > >
> > > > >
> > > >
> > > > _______________________________________________
> > > > Yale CAS mailing list
> > > > [email protected]
> > > > http://tp.its.yale.edu/mailman/listinfo/cas
> > > >
> > > >
> > >
> > >
> > > --
> > > -Scott Battaglia
> > >
> > > LinkedIn: http://www.linkedin.com/in/scottbattaglia
> > >
> > > _______________________________________________
> > > Yale CAS mailing list
> > > [email protected]
> > > http://tp.its.yale.edu/mailman/listinfo/cas
> > >
> > >
> >
> > _______________________________________________
> > Yale CAS mailing list
> > [email protected]
> > http://tp.its.yale.edu/mailman/listinfo/cas
> >
> >
>
>
> --
> -Scott Battaglia
>
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
>
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to