...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Warning | ||
|---|---|---|
| ||
This document is not longer maintained or valid. Please refer to the official CAS documentation at apereo.github.io/cas/ to learn more. |
| Table of Contents |
|---|
CAS Roadmap
The CAS Roadmap provides a common understanding regarding the what, why, and how of future CAS releases. Adopters use the roadmap to understand when a new version may be released, the changes they can expect, and based on the type of release, the difficulty or ease with which to upgrade. CAS developers use the roadmap to communicate with each other and the community the types of features, bug fixes, and improvements they are individually committed to working on.
...
3.5.x releases are conservative incremental changes for backward compatible bug fixes, enhancements and new features. CAS 3.5.0 was release released in July 2012. Deployers can expected on-going patch releases to the 3.5.x series.
...
- Marvin Addison, Virginia Tech
- Scott Battaglia, independent developer
- Unlicensed userJérôme LELEU, SFR (french telecom company)
- Unlicensed userMisagh Moayyed, Unicon via Cooperative Support
- Unlicensed user, Unicon via Cooperative Support
- Unlicensed uservia Open Source Support
- Andrew Petro
- William G. Thompson, Jr., Unicon via Cooperative Open Source Support
CAS 4.0 MAJOR Release
Schedule
- 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.
- move out the services management webapp from CAS server webapp -> Jérôme :
JASIG Issue TrackerJira Legacy server System JIRA serverId d8d429a7-dc92-3696-85f0-1de5d4e9bcf6 key CAS-1183 - make SAML support optional in a specific module -> Marvin / Jérôme :
JASIG Issue TrackerJira Legacy server System JIRA serverId d8d429a7-dc92-3696-85f0-1de5d4e9bcf6 key CAS-1188 - improve client protocols support -> Jérôme :
JASIG Issue TrackerJira Legacy server System JIRA serverId d8d429a7-dc92-3696-85f0-1de5d4e9bcf6 key CAS-1286 - improve OAuth server support -> Jérôme & Joe McCall :
JASIG Issue TrackerJira Legacy server
,System JIRA serverId d8d429a7-dc92-3696-85f0-1de5d4e9bcf6 key CAS-1288
JASIG Issue TrackerJira Legacy server
andSystem JIRA serverId d8d429a7-dc92-3696-85f0-1de5d4e9bcf6 key CAS-1282
JASIG Issue TrackerJira Legacy server System JIRA serverId d8d429a7-dc92-3696-85f0-1de5d4e9bcf6 key CAS-1287
Refactor Authentication APIs
Developer: Unlicensed userMarvin Addison
The present AuthenticationHandler/AuthenticationManager API components have served us well for approximately a decade. With a relatively small amount of engineering effort, we can build on these components to achieve some notable features in an elegant fashion:
...