CAS Clients

Owned by Brian Donnelly
Last updated: Jan 04, 2018 by Tom Poage (Unlicensed)

Casifying Web Servers and Applications

In this Section


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

mod_auth_cas

Yes

2.0

Yes

Windows IIS

CASAuthN

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

Ja-Sig Cas Client

Yes

2.0, 3

Yes

JSP

Ja-Sig JSP Client

Yes

2.0

No

PHP

phpCAS

Yes

2.0

Yes

Cold Fusion

CAS Cold Fusion Clients

Yes

2.0

No

ASP .NET

CAS ASP .NET Forms Authenticator

Yes

2.0

No

.NET

.NET CAS Client

Yes

2.0

No

Ruby on Rails

Ruby on Rails CAS Client

No

2.0

No

Perl

PerlCAS

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

Plone CAS Login

No

2.0

No

Drupal

Drupal CAS Client

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.