2010-08-11 Community Call

Attendees:

• Scott Battaglia
• Marvin Addison
• Benn Oshrin
• Dan Biondi
• Corey and Matt from University of Victoria
• Susan Bramhall

Moderator:

• Scott

Notetaker:

• Marvin

Agenda

• CAS Server Roadmap
• CAS Client Roadmap
• Changes for Next Month's Call
  • Community-Focused
  • Separate Developer Call
• New Documentation Rules
• Meet Ups
• UnConference
• Floor is Open

Notes

Scott related client updates.

• phpCAS just release 1.1.2 version.
• Java CAS Client release 3.1.12 targeted for next 2 weeks.
• .NET CAS Client on target for 1.0 release late summer early fall. Scott had some concern about versions in the wild. Marvin noted some of this confusion results from older version in OWA client. Will work with Bill Thompson, who is now on Steering Committee, to determine best course of action. One option is to roll OWA into .NET client.

Scott mentioned that Yale 2.x Java client questions have appeared on cas-user list recently and we discussed strategies for more clearly indicating that the Yale client is deprecated. Documentation changes can possibly be handled in context of documentation improvement efforts.

Scott related server updates.

• MFA design discussion continues among Scott, Yale, and Unicon principals. An API will be one outcome of the design work, with the API changes implemented over time. Changes to existing API components like CentralAuthenticationService will occur first with other integration points following in later versions.
• Unicon Cooperative Support resources are creating a mock UI/flow for 3.5. These will be posted to cas-dev for discussion.
• Partial SAML 2 support in 3.5.
• OpenID 2 support may make 3.5.

Susan proposed a change to Community Calls where an expert from the community presents a topic of interest. Many presentations would likely need collaboration software to share visuals. We would propose potential topics to the cas-user list for feedback. Devoting more time to questions is important; the presentation could possibly grease the wheels for discussion. We agreed that a 15 minute presentation would be the right length of time to allow for questions and general announcements.

We envision the MFA discussion evolving over time into a generalized developer call, possibly bi-weekly.

Scott suggested that the NYC-area meet up happen first since he could attend and possibly help work out kinks for subsequent meetings.