| Table of Contents |
|---|
...
- 2013-06-10: CAS 4.0 RC1, CAS 3.0 Protocol Revision RC1
- 2013-06-10 - 2013-07-12: Community testing and feedback. Additional release candidates as necessary.
- 2013-07-12: CAS 4.0 RC3
- 2014Q1: CAS 4.0 GA, CAS 3.0 Protocol Revision GA
...
CAS committers who attended the Jasig-Sakai 2012 conference in Atlanta arrived at rough consensus around a 4.0 release candidate with the following scope:
- improved authN APIs to support multiple credentials (forces Major release per release strategy)
- new skin and better support for mobile devices
- Improvements to the Ldap Password Policy enforcement that are described here.
- potentially other minor evolutionary improvements that would have been targeted for 3.6.
Other tasks planned for 4.0 :
- move out the services management webapp from CAS server webapp -> Jérôme :
Jira Legacy server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key CAS-1183 - make SAML support optional in a specific module -> Marvin / Jérôme :
Jira Legacy server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key CAS-1188 - improve client protocols support -> Jérôme :
Jira Legacy server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key CAS-1286 - improve OAuth server support -> Jérôme & Joe McCall :
,Jira Legacy server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key CAS-1288
andJira Legacy server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key CAS-1282 Jira Legacy server JASIG Issue Tracker serverId 76221f40-4501-3df1-8578-6c87908cbdf7 key CAS-1287
Refactor Authentication APIs
...