CAS Server 3.2 RC4

[Scott Battaglia]

No problem.  Let me know if it actually solves your problem :-). If not, we
can look into doing it in a separate thread.

-Scott

On Feb 5, 2008 4:30 PM, Lucas Rockwell <lr at berkeley.edu> wrote:

> Scott,
> I have not responded to this yet, so a very belated Thank You, for doing
> this!
>
> -lucas
>
> On Feb 5, 2008, at 12:16 PM, Scott Battaglia wrote:
>
> The ArgumentExtractors support injecting an HttpClient object which can be
> configured with timeouts.  The HttpClient will be used when contacting the
> external services to tell them to sign out.
>
> -Scott
>
> On Feb 5, 2008 2:54 PM, rg <rg4312 at gmail.com> wrote:
>
> > Can you provide a little more detail on "Single Sign Out supports
> > timeouts" or point me to the appropriate source changes.  I did a diff
> > on the 3.1.1 and 3.2RC4 directories, and I didn't see anything obvious.thanks,
> > -rg
> >
> > On Feb 4, 2008 11:43 AM, Scott Battaglia <scott.battaglia at gmail.com>
> > wrote:
> >
> > > CAS Community,
> > >
> > > We're pleased to announce the CAS 3.2 RC4 release.  If you're
> > > wondering if you missed RC1 - RC3, let's just say that it helps if you do
> > > your own internal testing before you tag stuff, not after. So let's just
> > > call RC1 - RC3, internal RCs ;-)
> > >
> > > So what's new in CAS 3.2 RC4?
> > >
> > > Updated dependencies: Log4j, Spring 2.5.1, Acegi Security 1.0.6,
> > > Spring LDAP, Spring Web Flow
> > > Bug Fixes: SPNEGO fixes, check ServiceManager enabled/disabled flag,
> > > Service Theme Resolver support for emtpy theme names,
> > > Enhancements: UTF-8 as the default in the PasswordEncoder, filtering
> > > for domain controllers in NtlmHandler. Single Sign Out supports timeouts,
> > > ability to enable/disable SSout
> > > New Features: Hard Timeout Expiration policy, updated Spring
> > > configuration so that you can drop a file in a specific directory and have
> > > it loaded automatically, Inspektr auditing tool
> > >
> > > If you're wondering why we went from CAS 3.1.2 to CAS 3.2, we felt
> > > that the changes to the configuration method and the addition of the new
> > > Inspektr tool (Note: it replaces the event handler example code, which was
> > > not considered production code.  Inspektr is considered a production
> > > codebase) sufficiently differentiated it from the CAS 3.1.x branch.
> > >
> > > You can download the files from here:
> > > http://www.jasig.org/products/cas/downloads/
> > >
> > > or http://www.jasig.org/downloads/cas/ (if the site isn't updated yet)
> > >
> > > Please provide any feedback (good, bad, or indifferent).  Again, the
> > > changes in the configuration as well as the usage of the Inspektr tool for
> > > auditing are relatively major changes, so anyone upgrading from CAS
> > > 3.1.1 to CAS 3.2 should be aware of this.
> > >
> > > Thanks
> > > -Scott
> > >
> > > --
> > > -Scott Battaglia
> > > LinkedIn: http://www.linkedin.com/in/scottbattaglia
> > > _______________________________________________
> > > Yale CAS mailing list
> > > cas at tp.its.yale.edu
> > > http://tp.its.yale.edu/mailman/listinfo/cas
> > >
> > >
> >
> > _______________________________________________
> > Yale CAS mailing list
> > cas at tp.its.yale.edu
> > http://tp.its.yale.edu/mailman/listinfo/cas
> >
> >
>
>
> --
> -Scott Battaglia
>
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>


-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20080206/aa10ca8b/attachment.html