CAS Server
Milestone 1 - January 24th, 2007
- RADIUS Support
- SPNEGO Support
- SAML 1.1 Support
- Attribute Support via SAML 1.1 (and later SAML 2)
- Re-architected procotol support to support multiple protocols concurrently.
Milestone 2
- Service Restrictions Support
- Password Management Support
Milestone 3
- SAML 2 Support
- Single Sign Out Support (via SAML 2?)
- SecurID Support
Release Candidate 1 - May 1, 2007
- Administration/Environment Screens
- Improved Internationalization
Final Release - June 15, 2007
- Apache 2 License (pending Board approval)
- Confirm that license/distribution information is correct.
- CAS List Migration to lists.ja-sig.org
- CAS Reference Guide
CAS Client
Milestone 1 - January 24, 2007
- SAML 1.1 Support
- Attributes Support
- Constructor clean up
Milestone 2
- SAML 2
- Single Sign Out Support
Release Candidate 1
- Internationalization
- Confluence Support
- JIRA Support
Final Release - June 15, 2007
- Client Reference Guide
- Apache 2 License
|
|
Not shown on this list yet: we are considering the effort involved in demonstrating "speaking" another protocol such as the CoSign protocol or the PubCookie protocol (or any other suggestions). If you have any ideas on this, please leave some comments.
Is it worth the effort to implement this, as opposed to simply documenting "daisy-chaining" methods? It is very simple to authN one ISO solution with another.
Also - considering the TGT passing component of CoSign (which is Kerberos-centric) - is it possible to implement the whole CoSign protocol, given that CAS is not Kerberos-centric, and would not necessarily have the Kerberos TGT available?
We're considering this because there are people who would love to deploy CAS but have an existing infrastructure to support. If CAS could run the new protocol and continue to support existing clients it would eliminate a maintenance burden on the teams (i.e. running two SSOs).
As for CoSign in particular, it was just an option. We're looking at adding support for at least one more protocol that is in common use.
Note: As a general principle, the CAS development is looking towards using open standards (or working with the standards groups) when introducing new features rather than modifying the existing CAS protocol.