Using mod_auth_cas at SFU

OVERVIEW

MOD_AUTH_CAS INTRODUCTION

mod_auth_cas is an Apache module that uses CAS to protect static and dynamic web content served by the Apache HTTP Server.

Note: There is an older version of mod_auth_cas that was extensively modified to work with SFU CAS. This version will still work, but is no longer supported. It only works with Apache 2.2, and that version of Apache is no longer being maintained by The Apache Software Foundation. If you are currently using the old SFU mod_auth_cas, and want to upgrade Apache to version 2.4, see the documentation here on moving from the old SFU mod_auth_cas to the new mod_auth_cas.

DETAILS

Once you have built and installed mod_auth_cas in your Apache modules directory (say /etc/httpd/modules), you would edit your Apache configuration to load the mod_auth_cas module with

LoadModule auth_cas_module modules/mod_auth_cas.so

You then need to add a few required parameters to configure mod_auth_cas

    CASLoginURL https://cas.sfu.ca/cas/login
     CASValidateURL https://cas.sfu.ca/cas/serviceValidate
     CASCookiePath /usr/local/apache2/cas/

mod_auth_cas needs to make a direct connection to the CASValidateURL to validate the Service Ticket from CAS when the user logs in. To allow the SSL connection to be made, you need to install the X509 certificate of the Certificate Authority for the CAS server in your certificate folder (default /etc/ssl/certs/). That certificate is available at ThawtePremiumServerBundleCA-2018-v3.pem. You would then specify the directory containing that certificate using:

CASCertificatePath /etc/ssl/certs/

You can then protect a directory in your Apache configuration by using:

<Location /secured>
   Authtype CAS
   Require valid-user
</Location>

You can also protect directories by placing the contents of the Location block in .htaccess files.

SUPPORTED REQUIRE DIRECTIVES