2009-06

Owned by ScottS
Last updated: Jun 18, 2009Version comment
2 min read

CAS Server

Upcoming 3.3.3 Release

We are currently finalizing the CAS Server 3.3.3 release, which will include multiple performance enhancements and bug fixes, including improved JPA Ticket Registry clean up and single sign out performance.

We are expecting this to be released shortly.

4.x Branch Development

Work continues on the next generation CAS release. Recent additions to the CAS4 codebase include support for JPA, Memcached, and Memory-backed storage mechanisms, an overhauled UI Support for JPA, Memcached, and Memory-backed storage mechanisms have been completed.

You're invited to try out the code and provide feedback, suggestions, etc.

CAS Clients

phpCAS

phpCAS 1.1 RC1 has been released with multiple enhancements including support for the samlValidate, which would allow a phpCAS client to access the attributes returned in a SAML 1.1 response.

The release can be downloaded here: http://www.ja-sig.org/downloads/cas-clients/php/1.1.0RC1/

Java Client

Just a reminder, that the Jasig CAS Client for Java is available both in the public Maven Repositories, as well as on the Jasig Download Site: http://www.ja-sig.org/downloads/cas-clients/cas-client-3.1.6-release.zip

Maven users should use the following:
GroupID: org.jasig.cas
ArtifactId: cas-client-core
Version: 3.1.6
Type: jar

CAS Community Calls

Recent community calls involved discussions on potential incubation projects including a .NET client, ClearPass, and more. The steering committee will be looking into properly labeling available clients.

In addition, RFCs were discussed. RFC1, related to the removal of unique identifiers, seemed appropriate (separate question of whether there should be an RFC to remove all query string parameters). The second RFC, related to separating UI related elements from the CAS protocol had no opinions. The third RFC was related to locking down service urls. This seemed more of a feature of the CAS server then a protocol extension because the protocol would have to be changed for each protocol.

Community calls will be held on the second Wednesday of the month at 2PM Eastern, although we will confirm beforehand if there are discussion topics.