CAS Clients
Casifying Web Servers and Applications
A CAS authentication module is likely available for most modern web servers and programming languages, and a number of common web-applications have CAS authentication modules available.
Compatibility Matrices
Web Servers
A CAS client exists for the most common web servers. However, these clients have been implemented independently and exhibit a variety of features and configurations.
Server | Client | Supported | CAS Protocol | Single Sign Out |
|---|---|---|---|---|
Apache 2.x | Yes | 2.0 | Yes | |
Windows IIS | Yes | 2.0 | No |
Web Programming Languages
CAS authentication can be integrated with the majority of web programming languages. These code modules provide a client interface to allow a web application to enforce and consume CAS authentications.
Language | Client | Supported | CAS Protocol | Single Sign Out |
|---|---|---|---|---|
Java | Yes | 2.0, 3 | Yes | |
JSP | Yes | 2.0 | No | |
PHP | Yes | 2.0 | Yes | |
Cold Fusion | Yes | 2.0 | No | |
ASP .NET | Yes | 2.0 | No | |
.NET | Yes | 2.0 | No | |
Ruby on Rails | No | 2.0 | No | |
Perl | Yes | 2.0 | No |
Web Applications
CAS authentication modules have been packaged for a number of open source and commercial web applications.
Application | Client | Supported | CAS Protocol | Single Sign Out |
|---|---|---|---|---|
Zope / Plone | No | 2.0 | No | |
Drupal | No | 2.0 | Unknown |
Matrix Key
- CAS Protocol: CAS has gone through two revisions of its ticket-validation protocol since its inception. The CAS 1.0 protocol used plaintext response values that could be parsed to determine if authentication succeeded. CAS 2.0 introduced an XML-formatted response packet. Our CAS service supports both protocols, so either is acceptable.
- Single Sign Out: New to CAS 3.1 is a single-sign-out feature. This feature allows services to direct the user to a single-sign-out url, at which point the CAS service will call back each application the user CAS-authenticated to, indicating that the local session should be destroyed.