1. CAS Update Jasig 2011 Marvin Addison Susan Bramhall Andrew Petro Bill Thompson

2. CAS Server 3

3. 3.4 maintenance branch 3.4.8 tagged, but 3.4.7 latest marketed GA release Bugfix releases LoginTicket restored to protocol compliance

4. Improve Services Management UI?

5. CAS 4 Goals, Design, and Features Marvin Addison Middleware Services Virginia Tech May 24, 2011

6. 2011-05-24CAS 4 Goals, Design, and Features6 Goals Multiprotocol support by design CAS protocols SAML 1.1 and SAML 2 OpenID Support important/emerging use cases User messaging (e.g. password expiration) Multi-factor authentication Federation Add extension points with richer APIs

7. 2011-05-24CAS 4 Goals, Design, and Features7 Change Hurts

8. 2011-05-24CAS 4 Goals, Design, and Features8 Component Name Changes CAS 3CAS 4 TicketGrantingTicketSession (implied)Access ServiceTicketTokenServiceAccessRequest TicketRegistrySessionStorage

9. 2011-05-24CAS 4 Goals, Design, and Features9 Name Change Rationale Concise, accurate names clarify the API Names distill common features of all (planned) protocols Avoid overloading names (e.g. Ticket) Name implied but important concepts (e.g. Access)

10. 2011-05-24CAS 4 Goals, Design, and Features10 Richer Component Interfaces Core layers remain same Authentication Ticket (Session) management Service management Layers exchange *Request/*Response messages Factories help tame dependencies

11. 2011-05-24CAS 4 Goals, Design, and Features11 Login Example Credential s SW F POST CntrAuthSvc LoginRequest LoginResponse AuthenticationManager AuthenticationRequest AuthenticationResponse

12. 2011-05-24CAS 4 Goals, Design, and Features12 What Can We Do With It?

13. 2011-05-24CAS 4 Goals, Design, and Features13 Password Expiration Warnings Two key API components collaborate GeneralSecurityExceptionTranslator LoginResponse MicrosoftActiveDirectoryGeneralSecurityExceptio nTranslator translates LDAP exception for password expired into CredentialExpiredException LoginResponse#getGeneralSecurityExceptions() available to view layer for user display

14. 2011-05-24CAS 4 Goals, Design, and Features14 Multifactor Authentication Key enablers are support for multiple credentials in LoginRequest and storage of multiple authn exeptions in LoginResponse The Map is fundamentally important for SWF processing and user interaction Details of user interaction (e.g. how to upgrade existing credential) not well understood

15. 2011-05-24CAS 4 Goals, Design, and Features15 Work in Progress CAS 4 is undergoing active development We MUST get new APIs right Peer review and collaboration essential to success – is your use case covered? Feedback welcome on cas-dev@lists.jasig.orgcas-dev@lists.jasig.org https://source.jasig.org/cas3/trunk

16. Client Libraries

17. 17 CAS Clients – Official Acegi (Spring Security) CAS Client for Java 3.0/3.1 mod_auth_cas (Apache) PhpCAS.NET CAS Client (almost official...) Official Clients Generally being actively developed and maintained. Likely to get support on the cas-user list.

18. 18 CAS Clients – Unofficial.Net Http module ASP.NET Forms Authentication AuthCASCAS + Seam Web Applications CASP Adds CAS Logic to an ASP.NET AppCAS Proxying with ASP.Net Forms Authentication CherryPy CAS ClientColdFusion CAS Client ComponentColdFusion client script Google Web Toolkit - GWT CAS ClientjAPS 2.0 CAS Clientmod_python auth module Perl ClientPrado clientPycasRuby on Rails CAS ClientSeraph as CAS Client Soulwing CAS ClientSoulwing Java CAS ClientSymfony CAS Client VBScriptVirginia Tech CAS ClientsWebObjects Client https://wiki.jasig.org/display/CASC/Unofficial+CAS+Clients Unofficial Clients Essentially all of the clients people have let us know about, that may or may not be in active development anymore, and may solve a niche need. You should use these at your own risk. Many are excellent clients, but may no longer be supported any more. Others are purely theoretical examples of of how a client would function.

19. 19 CAS Clients – Incubating.NET CAS Client (almost official...) CASBar – Toolbar for Firefox 2 Official Clients Incubating Clients are new clients that are under development, and which may become official clients. They're up-and-coming clients that we're paying attention to, have petitioned the Steering Committee to become official clients, and often have active members on cas- user.

20. 20 CAS Clients – Legacy Yale CAS Client Apache Module PAM PL/SQL Legacy Clients In many cases, no longer actively developed, but still function quite well (i.e. the PAM module). In other cases, they've been superseded by newer clients (i.e. The Jasig CAS Client for Java). You will still find many people on cas-user who are familiar with these modules, but many have migrated to the newer code.

21. 21 CAS Clients – CASifying Apps Apache OFBiz Joomla 1.5 OpenCms OpenReports SharePoint & ASP.NET Web Sites WebAdvisor Confluence as CAS Client EZPublish Fisheye and Crucible Oracle Calendar web client with mod_cas Oracle Portal Oracle 11i applications qmail-ldap+webmail Mediawiki (with phpCAS)Outlook Web Access 2 PeopleSoft phpBB3 (phpBB v3) phpGroupware Sakai Sun Identity Manager Tomcat Manager Roller weblogger Tomcat uPortal Client WordPress Client Zimbra Zope client https://wiki.jasig.org/display/CASC/CASifying+Applications CASifying Apps Describes some unofficial instructions, many contributed by users, on how to CASify particular applications.

22. 22 CAS Clients – CASified Apps uPortal Mantis pNews Sympa TikiWiki Mule Claroline Moodle Liferay Portal ILIAS Learning Management Chamilo Simply Voting BlueSocket https://wiki.jasig.org/display/CASC/CASifying+Applications CASified Apps Project / Vendor maintained CAS integration. Works out- out-of-the-box!

23. Documentation

24. Your feedback / Discussion / Questions

25. 2011-05-24CAS 4 Goals, Design, and Features25 Questions