Central Authentication Service

This is community space for the JA-SIG sponsored CAS efforts. See press release.

Introduction - What is CAS?

CAS is an enterprise Single Sign-On solution for web services. Single Sign-On (SSO) means a better user experience when running a multitude of web services, each with it's own means of authentication. With a SSO solution, different web services may authenticate to one authorative source of trust, that the user needs to log in to, instead of requiring the end-user to log in into each separate service.

A number of out-of-the-box solutions exist to enable web services written in a specific language, or based on a framework, to use CAS. This would enable deployers to implement a SSO solution in a matter of hours.

The CAS Project

• CAS Roadmap
• CAS Server Releases
• Mailing Lists
• Wishlist

CAS Source

• FishEye view on the CAS 3.0 source tree
• Obtaining the CAS Source

Architecture

• CAS 1 Protocol/Design
• CAS 2 Protocol/Design novelties (proxy, etc.)
• Detailed Protocol Specification
• Proxy Authentication
• Proxy CAS Walkthrough

CAS 3

• CAS3 object model
• CAS3 Design and Development
• Shawn Bayern's early CAS and SAML document
• CAS 3 User Manual

CAS Implementations

 CAS Back-end examples

To get the most out of your CAS server, you'll most likely wish to implement a specific bac-end, like LDAP, some RDBMS, etc. Please refer to the Examples to Configure CAS page, and find some detailed explanations on back-end configuration. Please feel free to add your own too.

Other CAS Server Implementations

• ESUP-Portail quick-start distribution
• RubyCAS-Server - A full-featured alternative to the JA-SIG CAS server, written in Ruby.

CAS Server extensions

• cas-spare, a system for automating CAS server failover

More documentation

• Solving SSL issues
• Powerpoints
• Adding "Public Workstation" vs "Private Workstation" Timeouts

Community

This Confluence Wiki

Click here for information about this Wiki, including how you can contribute.

Who uses CAS?

• CAS Deployers
• What kind of resources does it take to deploy CAS?

CASifying Applications

CAS Clients Wiki

Experiences CASifying applications

• CASifying Apache Pluto portal driver
• CASifying IBM WebSphere ( WAS ), Websphere Portal Server ( WPS ) or WebSphere Content Management ( WCM ) using the Trust Association Interceptor API ( TAI )
• CASifying Joomla 1.5
• CASifying Outlook Web Access
• CASifying PeopleSoft
• CASifying phpBB3 (phpBB v3)
• CASifying phpGroupware
• CASifying Sakai
• CASifying Sun Identity Manager
• CASifying Tomcat Manager
• CASifying Trac
• CASifying TWiki
• CASifying Wordpress
• CASifying Zimbra

Oracle applications

• CASifying Oracle Calendar web client with mod_cas
• CASifying Oracle Portal
• CASifying Oracle 11i applications

ESUP-Portail distributions of CASified applications

The ESUP-Portail download site offers links to a CASified Horde, a CASified phpBB, a CAS proxy for Sun One Calendar, and a CAS proxy for Apogee Web.

Applications that come CASified

• uPortal - our own open source portal
• Mantis
• pNews - a newsreader.
• Sympa - a mailing list manager.
• TikiWiki - a Wiki and much more.
• Mule - an Enterprise JavaBean messaging framework. CASified by virtue of use of Acegi.
• Claroline - a free PHP / MySQL collaborative learning environment for creating and administering courses through the web. GPL. CASified out of the box as of 1.7.
• Moodle - a free, open source course management system (CMS). Courseware. CAS as a standard authentication module.
• Liferay portal - a free, open source portal.

Hardware products that come CASified

• BlueSocket

Other Miscellaneous topics

• Using CAS without the CAS login screen
• CAS Java Client Gateway Example

Other Web SSO products

The Central Authentication Service isn't the only Web SSO product around. This page provides links to some other Web SSO products.