CAS Status and Roadmap

Created by Brian Donnelly
Last updated: Aug 07, 2008 by HamptonH (Unlicensed)Version comment

CAS Status

A recent 24 hour load test of the single server configuration generated 2 million successful authentications at an average rate of 22.6 authentications per second. This far exceeds the performance of Distauth under peak load.

Given the stability of the current CAS service, the robust load test results and the single point of failure associated with Distauth, IET would like to begin promoting the migration of campus applications to CAS after June 19th, 2008. While the service is open for anyone to use, we have a few items on the CAS roadmap that we would like to accomplish prior to broad campus adoption, which we feel can be accomplished by June 19th (primarily to reduce support loads).

CAS Roadmap

  • June 19th
    • A web server/OS compatibility matrix (Complete)
    • A standard feature set for all CAS clients (Complete)
    • Instructions for implementation and use (Complete)
    • A CAS Service Registry (Complete)
  • End of Summer
    • Clustered Configuration for High Availability (IET's practice is to deploy enterprise level services in multi-server pools or clusters to ensure the highest possible uptime). At this time, the DEV clustered environment does not provide the same authentication rate as a single server configuration.
    • Restrict CAS authentication services to those applications registered in the CAS Service Registry
    • Open test environment to the campus technical community

If you have any questions regarding the status of CAS in the future, please contact Hampton Sublett, Middleware Program Manager at hsublett@ucdavis.edu. If you have technical questions, please contact Brian Donnelly, lead CAS developer, at: bdonnelly@ucdavis.edu