Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Warning
titleDeprecated

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.

...

...

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
    System JIRA
    serverId
    76221f40
    d8d429a7-
    4501
    dc92-
    3df1
    3696-
    8578
    85f0-
    6c87908cbdf7
    1de5d4e9bcf6
    keyCAS-1183
  • make SAML support optional in a specific module -> Marvin / Jérôme : 
    Jira Legacy
    server
    JASIG Issue Tracker
    System JIRA
    serverId
    76221f40
    d8d429a7-
    4501
    dc92-
    3df1
    3696-
    8578
    85f0-
    6c87908cbdf7
    1de5d4e9bcf6
    keyCAS-1188
     
  • improve client protocols support -> Jérôme : 
    Jira Legacy
    server
    JASIG Issue Tracker
    System JIRA
    serverId
    76221f40
    d8d429a7-
    4501
    dc92-
    3df1
    3696-
    8578
    85f0-
    6c87908cbdf7
    1de5d4e9bcf6
    keyCAS-1286
  • improve OAuth server support -> Jérôme & Joe McCall : 
    Jira Legacy
    server
    JASIG Issue Tracker
    System JIRA
    serverId
    76221f40
    d8d429a7-
    4501
    dc92-
    3df1
    3696-
    8578
    85f0-
    6c87908cbdf7
    1de5d4e9bcf6
    keyCAS-1288
    Jira Legacy
    server
    JASIG Issue Tracker
    System JIRA
    serverId
    76221f40
    d8d429a7-
    4501
    dc92-
    3df1
    3696-
    8578
    85f0-
    6c87908cbdf7
    1de5d4e9bcf6
    keyCAS-1282
     and 
    Jira Legacy
    server
    JASIG Issue Tracker
    System JIRA
    serverId
    76221f40
    d8d429a7-
    4501
    dc92-
    3df1
    3696-
    8578
    85f0-
    6c87908cbdf7
    1de5d4e9bcf6
    keyCAS-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:

...