2010-07-21 Community Call

Owned by ScottS
Last updated: Jul 21, 2010Version comment
2 min read

2010-07-21 Community Call

Dial-In Information: 12:00 pm Eastern (11:00 am Central)
Conference Bridge: (641) 715-3200 640123#

Attendees:

Joachim Fritschi
Bill Thompson
Scott Battaglia
Cory & Matt University of Victoria
Ray and Jeremy from Simon Fraser
Bill Clark, Raymond Duncan, et al West Texas

Note Taker: Kim
Moderator: Scott

  1. CAS Server Roadmap and Updates - work on 3.5 is progressing but no ETA yet
    • New APIs
    • New Supported Features
    • Multifactor Support - API support will be in 3.5, but underlying policies will need to wait for 3.6.
    • Weekly calls with Yale are taking place on development and others with interest are invited to join.
  2. CAS Clients - if you're using a client framework, please help the developers with testing.
    • .NET Client
      • Hoping to do a 1.0 release in August.
      • For that release code is documented, updated for .Net 2 framework, removed partially implemented features, fleshed out the example website to make it use all the current features, fixed a bug regarding port numbers in service URLs and more.
    • phpCAS Client
      • Community was asked to test the 1.1.2RC2 release which will be ready for end of July release if there is feedback from testers. There is also a preliminary test suite for testers to use.
      • Feature release 1.2 is in development, for php5 only.
      • A version 2 release is contemplated, perhaps on a different code base, to provide modularity and scalability.
    • Java Client
    • mod_auth_cas
      • No updates lately; maintainer may be awaiting permission from employer to do commits to the project.
  3. New Documentation Rules that will go into effect soon (not discussed?)
  4. Mailing list issues (not discussed?)
  5. The Jasig CAS Securing Your Server Page was prepared by Scott and the community is invited to contribute to the documentation on this page.
  6. Questions, Ideas, Open Floor, etc. (though feel free to ask questions throughout)
    1. Suitability of 3.4.2 for production was discussed:  it is in production at several places, but Scott noted some issues to check for before migrating from 3.3.5.
    2. CAS OWA requires the confluence of C# and advanced IIS skills beyond that of the average exchange administrator and this issue comes up repeatedly on the cas-user lists. It was suggested that some brainstorming take place to see if the project could be made easier for exchange admins or non-C# CAS admins to install. Bill suggested some documentation be added to the project on gitHub. Scott suggested that Jasig hosting it and taking it as a project might be a way to upgrade support; Bill and Scott agreed an additional maintainer for that project would be required.
  7. The UnConference and CAS meetups were discussed and the community invited to contribute topics to the UnConference and to organize CAS meetups.