Bio
I've worked at the University of South Florida for 13 years, beginning in the IT help desk and moving up the ranks to become the lead Unix System Administrator for the student system. I first implemented CAS as part of the effort to outsource student Email to Google and it has quickly become the standard SSO technology for all new IT projects at USF. As a result of my work with CAS and the GoogleApps outsourcing project, I have been put in charge of the technical team for our Identity Management efforts, including developing CAS extensions. This new position has also given me the opportunity to be involved with higher education communities such as Jasig, InCommon and Internet2. I was fortunate enough to be selected as a member of the CAS steering committee last year and I feel that we have worked very well together.
Platform Statement
The main points that I think need to be addressed by the CAS steering committee this year are all related to promoting the use and development of CAS:
- Attracting more developers to work on the CAS server and to add support for CAS4 features (SAML, etc) in the 'official' clients
- Producing promotional material demonstrating the features and benefits of using CAS
- Increasing the number of officially supported CAS clients
- CAS4 and other SSO projects (Shibboleth, OpenSSO, etc) have some common features - What can be done to work together with other groups to coordinate efforts and minimize duplication of effort?