...
Improve Default Ticket Granting Ticket Expiration Policy
Developer: Unlicensed userWilliam G. Thompson, Jr. via Cooperative Support and in partnership with Lamar University
JIRA: CAS-1032
CAS 3.4.10 introduced a new ticket expiration policy for ticket granting tickets that provides both a fixed and sliding window. Further background on the development of this policy is available on CAS-1003. The driver for this enhancement is a requirement from Lamar University for better control over the TGT expiration policy. This improvement ensures that TGTs will eventually expire at a fixed time.
ClearPass
Developer: Unlicensed userAndrew Petro, Unicon via Cooperative Support
...
LDAP Password Policy
Developers:
- Unlicensed userWilliam G. Thompson, Jr. via Cooperative Support and in partnership with Lamar University
- Unlicensed userAndrew P Tillinghast
JIRA: CAS-948
Make LDAP Password Policy a configurable feature and part of the Jasig CAS 3.5 distribution.
EhCacheTicketRegistry
Developers:
JIRA: https://issues.jasig.org/browse/CAS-1076
...
CAS Service Registry Improvements
Developers: Unlicensed userAndrew Petro, Unlicensed userDmitriy Kopylenko, Unlicensed userMisagh Moayyed, Unicon via Cooperative Support
...
A kinder, gentler, more usable Services Registry with some features that make it more friendly for CAS adopters.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Jira Legacy | ||||||
|
| Jira Legacy | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Jira Legacy | ||||||
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Jira Legacy | ||||||
|
| Jira Legacy | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
| Jira Legacy | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
| Jira Legacy | |||||||
|
Switch to Apache 2.0 license
Developer: Unlicensed userAndrew Petro, Unicon via Cooperative Support
...
Improved skinnability
Developer: Unlicensed userJacob Lichner with support from Unlicensed userAndrew Petro
Broad initiative for CAS 3.5 tracked in CAS-1061, with specific JIRA issues for trackable changes to be determined.
| Jira Legacy | |||||||||
|---|---|---|---|---|---|---|---|---|---|
|
All CAS adopters need to skin their CAS instance. Additionally, CAS has a "themes" feature with support for per-service themes. A minor version bump from CAS 3.4.x to 3.5 is an opportunity to incur minor upgrade pain (necessitating adopter changes to their skins) in exchange for worthwhile improvements in the ease, simplicity, clarity of skinning and skinning features. Working towards 3.5 release, examine present state of features and practices for CAS skinning and themeing, and how to evolutionarily improve consistent with a 3.5 release.
...
Upgrade to Spring 3.1 and check all dependent libraries for current versions
Developer: Unlicensed userDmitriy Kopylenko, Unicon via Cooperative Support
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Enhance Monitoring and Management Capabilities
Developer: Unlicensed userMarvin Addison, Virginia Tech
It would be helpful, particularly for enterprise and HA deployments, to expose Web service and/or JMX monitoring and management facilities for CAS to support common enterprise management and monitoring concerns such as the following:
...
The specific implementation of management and monitoring functionality is second to the requirement that they are fundamentally scriptable and compatible with tooling.
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
CAS 4.0 MAJOR Release
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:
...
Refactor SSO Session Management
Developers: Unlicensed userScottS, Unlicensed userMarvin Addison
Refactor SSO session management with the following design goals:
...
Enhance Single Logout Capability
Developer: Unlicensed userMarvin Addison
The existing single sign-out/logout (SLO) capability is based on the SAML 1.1 specification and should be updated to conform with the SAML 2 Single Logout Profile (section 4.4 of the SAML2 Profile document). In particular it would be very helpful for HA deployments to be able to use the front channel binding to avoid host affinity issues that arise from the existing back channel communication mechanism.
...
SAML2 Support
Developers: Unlicensed userScottS, Unlicensed userMarvin Addison
The CAS sever should provide first-class support for the following SAML2 specifications:
...