CAS 3
- Andrew Petro
- ScottS
Owned by Andrew Petro
CAS 3 is a next-generation implementation of the Central Authentication Service.
Documentation
- CAS 3 JA-SIG pre-conference seminar
- CAS 3 JA-sIG Pre-Conference Seminar Slides - December 2005
- CAS for Deployers
CAS 3 Releases
- See Releases page.
Issue tracking
Project roadmap
Yale-Rutgers Meetings
In September 2004 Rutgers New Technology Group visited Yale to open discussions on the CAS 3 project.
On 24 January 2005 Yale and Rutgers held the first of what are expected to be bi-weekly video conferences for this project.
- 2005-01-24 Yale-Rutgers Video Conf — Initial video conference.
- 2005-02-09 Yale-Rutgers Video Conf — Releasing M1 and planning M2.
- 2005-02-24 Yale-Rutgers video conf — WIND, SAML, M2
- 2005-03-10 Yale-Rutgers video conf — Login, authentication exceptions, M2
- 2005-03-24 Yale-Rutgers video conf — noon - 2pm
- 2005-04-07 Yale-Rutgers video conf — 1pm - 3pm
- 2005-04-21 Yale-Rutgers video conf — Documentation, compatibility testing, SAML ticket validation responses, Single Sign Out, Spec, client cert credentials
- 2005-05-05 Yale-Rutgers video conf — 1pm - 3pm
- 2005-05-19 Yale-Rutgers video conf — 1pm - 3pm
- 2005-06-02 Yale-Rutgers Face to Face Meeting
- 2005-06-02 Yale-Rutgers video conf — 1pm - 3pm
- 2005-06-16 Yale-Rutgers video conf — 1pm - 3pm
- 2005-06-30 Yale-Rutgers video conf — Postponed.
- 2005-07-28 Yale-Rutgers Teleconf
Yale Meetings
The Technology & Planning group has been meeting internally to discuss CAS 3, attempt to better understand the Rutgers CAS3 milestone code and use cases, better understand CAS/Shib integration, etc. These are notes from some of these meetings:
- 2005.01.07 Yale Discussion — CAS ticket package. There are only GrantingTickets and ServiceTickets. All tickets have (possibly null) grantors.
- 2005.01.10 Yale Discussion — AuthenticationHandler API
- 2005.01.12 Yale Discussion — CAS3 web package
- 2005.01.19 Yale CAS discussion — AuthenticationHandler.supports() , authentication types
- 2005.01.24 Yale CAS discussion — Shibboleth/CAS integration. SAML. CAS 3 protocol.
- 2005.01.31 Yale discussion
- 2005.02.02 Yale discussion
- 2005.02.04 Yale Discussion
- 2005.02.23 Yale Discussion
- 2005.03.02 Yale Discussion
- 2005.03.07 Yale Meeting — Non-interactive login. LoginConfig.
- 2005.03.16 Yale Discussion
Random other content
expected CAS3 Milestones
Milestone 1:
Purpose of Milestone 1: Demonstrate that CAS 3 is a viable architecture upon which to build and is a working implementation of CAS 1 and CAS 2 functionality.
CAS 1.0 backward-compatibility
- Documentation detailing CAS 1.0 protocol
- Functional tests demonstrating CAS 1.0 protocol compliance
- CAS 3.0 Milestone 1 fully implements CAS 1.0 protocol
CAS 2.0 backward-compatibility
- Documentation detailing CAS 2.0 protocol
- Functional tests demonstrating CAS 2.0 protocol compliance
- CAS 3.0 Milestone 1 fully implements CAS 2.0 protcol
Authentication Handlers
- At least two real working authentication handlers demonstrating pluggability. Actual handlers TBD, natural candidates include Kerberos and the technology Rutgers uses in production
- Dummy authentication handler which authenticates usernames matching passwords, for demo purposes
- Adaptor allowing any CAS 2.0 PasswordHandler implementation to be plugged in to CAS 3.0.
Demo-readiness
- CAS 3.0 Milestone 1 build delivers a .war that can be dropped into Tomcat and be deployed and testable without modification. The .war may require being accessed over SSL, as CAS 2.0 does.
- A currently CASified application can be switched to authenticate via a CAS 3 Milestone 1 deployment merely by changing its configuration to point at the URL of the server – no other reconfiguration required.