Sevrer

Server Deployment
Installing How to Write an AuthenticationHandler Customizing Views LDAP Authentication Handler Client Certificates Clustering Local Customizations Solving SSL Issues 2 4 11 12 16 25 26 28

i

Server Deployment
/server/index.xml

1

Server Deployment
In this section, you'll find mini-guides about various parts of the deployment process for CAS, including installing,clustering, and customizing. You can download the complete Server Deployment Guide in PDF format.

Server Deployment

Installing
/server/installing/index.xml

2

Installing CAS
Gather Dependencies
To install CAS on a machine for deployment, the following external applications are needed: • Java 1.4.2 or higher • Apache Tomcat 5.x To include customizations to your CAS deployment, thefollowing applications will be needed to compile and package the CAS war file: • Apache Ant Finally, you'll need a copy of CAS itself. The most recent version of CAS can be found in the Download section.

Demo-ing CAS
If you only wish to demo CAS, a demo WAR file is included with each distribution in the ${project.home}/target directory. You can merely deploy this WAR file to a Tomcat instance.Working with CAS
If you plan on deploying CAS locally, and wish to use SSL, please see our SSL guide for setting up a self-signed SSL certificate. Note that if you plan on putting CAS in production you must use SSL. For adding your own custom AuthenticationHandler, please see our guide on writing custom plug-ins for CAS. To edit the default JSP pages to make them look like your company orinstitution's, look in the ${project.home}/webapp/WEB-INF/views directory.
Server Deployment

Installing
/server/installing/index.xml

3

To build a war file of your custom changes, navigate to the ${project.home}/localPlugins directory. Then execute "ant war". This should generate a WAR file with your custom modifications. This WAR file can be deployed in Tomcat.

Server Deployment

Howto Write an AuthenticationHandler
/server/authenticationhandler/index.xml

4

How to Write an Authentication Handler
The Domain of Authentication
Before we discuss actual APIs and code, it may be helpful to review the concepts of CAS authentication. Credentials Credentials are what someone presents to CAS as evidence on the basis of which they may be authenticated. A username, password pairis a Credentials, as is a cryptographic certificate, etc. Principal A Principal is an entity that is authenticated.

Coding
AuthenticationHandler
The core interface to implement for your authentication-handling plugin is AuthenticationHandler.
/** * Validate Credentials support for AuthenticationManagerImpl. * * Determines that Credentials are valid. Password-based credentials may be * testedagainst an external LDAP, Kerberos, JDBC source. Certificates may be * checked against a list of CA's and do the usual chain validation. * Implementations must be parameterized with their sources of

Server Deployment

How to Write an AuthenticationHandler
/server/authenticationhandler/index.xml

5

information. * * Callers to this class should first call supports to determine if the *AuthenticationHandler can authenticate the credentials provided. * * @version $Revision: 1.11 $ $Date: 2005/06/17 13:24:38 $ */ public interface AuthenticationHandler { /** * Method to determine if the credentials supplied are valid. * * @param credentials The credentials to validate. * @return true if valid, return false otherwise. * @throws AuthenticationException An AuthenticationException cancontain * details about why a particular authentication request failed. */ boolean authenticate(Credentials credentials) throws AuthenticationException; /** * Method to check if the handler knows how to handle the credentials * provided. It may be a simple check of the Credentials class or something * more complicated such as scanning the information contained in the * Credentials object. * *...