...
- CAS Server Roadmap and Updates
- CAS server 3.5 will include major re-factoring of core APIs (trunk is currently broken). CAS is moving towards multiprotocol single sign-on provider so using more generalized names. For example ticket nomenclature will disappear; session becomes a primary domain object. A goal is a very lightweight core API moving heavier dependencies to various implementations.
- It would be helpful to lay out new module structure and thinking about future thinking.
- Wiki home page clean up. It would be nice to file JIRA for documentation issues. Pat agrees to do that. CAS wiki - what is the purpose? A developer space, perhaps. This space needs to be cleaned up. Marvin willing to start work on this by reorganizing top level page. Scott and others can then update content appropriately.
- CAS Client
- .NET Client - currently in incubation and Marvin will update incubation status by Monday 5/17.
- phpCAS Client - Joachim from Germany - new lead for php CAS client. He is looking for assistance. Stabilize 1.3 1 tree and expects to start with new branch for future road map. VT can help test. Folks recommend announcing intentions to CAS-dev list and CAS-user list. Jonathan asks news go to news@jasig. Joachim will also let steering committee know his plans and needs.
- Plug for ACAMP
- Identity management issues under auspices of In Common and Jasig. Now closed at 75 people due to so much interest! Waiting list is coming.
...