This directory contains the mod_cas distribution for Texas A&M University

Please read the README file in this directory for a more thorough treatment of mod_cas
and how it interacts with the Apache server.  There are several http.conf parameters
that need to be reviewed as well as the .htaccess file for the directory that needs
the authorization.

Also, please note that ssl_client.c needs to be updated to suit your specific needs.

In operation, the mod_cas module will call the legacyValidate service of CAS to check for a valid login.
The response string is the standard string from CAS, that is, a "yes" or "no" at the start
NetID and UIN, in a more or less XML construct.  

Developers must tailor the mod_cas module for their specific needs.  That is, the module 
will store a value in the output buffer that ultimately becomes the authorized user header
in the HTTP stream.  You can either store the NetID or the UIN or a concatenation of the two.
Your web application will then have to tailored to accept this value and process the string.
If you need the UIN for accessing a database or access list, then you will want to store the
UIN in the output buffer.  If you need the NetID then that is the value to store.  In some 
cases, you may want both.  For this case, I would suggest you concatenate the two values, 
with the UIN at the end, and then in your web application parse the field to extract the 
two separate parts.

Of course, if all that is required is a valid login, then it really does not matter what is
stored in the output field.

A sample program, testit.c, is included for testing various combinations of NetID
and UIN.  This program allows you to test various parsing strategies before updating the
ssl_client.c code.