This Page Represents HYPOTHETICAL Scenarios Only
The scenarios described here are for discussion purposes only. They are not intended to reflect real scenarios known to the StratOrg team.
Background
CAS is a mature WebSSO project distributed under an Apache 2 license and housed at Jasig. CAS is maintained primarily through volunteer efforts of higher ed and non-higher ed participants, with some work funded through Unicon's cooperative support model.
Hypothetical Request
The CAS steering committee has long contemplated adding SAML support. While CAS and Shibboleth work well together, the overhead of running two SSO products is obviously higher than of running one. While Shibboleth supports SAML, CAS is widely perceived as easier to support and integrate. Adding SAML support would require approximately 1 FTE over 6 months.
Execution
CAS adds a project to the Authentication Workstream for SAML support. This project may be resourced by
- An investor specifically earmarking funds (less shared services tax) towards that project
- An investor providing developer FTE to the project in accordance with existing developer guidelines
- The Joint Venture governance committee earmarking funds from the authentication workstream (according to JV resourcing policy)
None of these options imply changes to the existing CAS steering committee.