Turns WordPress or WordPress MU into a CAS single sign-on authenticator.

Casey Bisson

Matthew Batchelder

<p>This plugin reserves a collection of URIs that create, validate, and destroy CAS tickets.</p>
<ul>
<li>
<p>/cas/login :: If user is not authenticated he/she is redirected to the login page.  Otherwise the user is redirected to the service specified as a GET variable in the URL – or if service is not provided, the user is redirected to the WordPress instance’s home.</p>
</li>
<li>
<p>/cas/logout :: The user’s session is destroyed, user is logged out of the WordPress instance, and redirected to $_GET[‘service’] (or the blog home if service isn’t provided)</p>
</li>
<li>
<p>/cas/proxyValidate and /cas/validate :: The CAS ticket must be passed as a GET parameter in the URL when calling /cas/validate.  The ticket is validated and XML is output with either cas:authenticationSuccess or cas:authenticationFailure</p>
</li>
</ul>
<h3>Hooks & Filters</h3>
<h4>wpcas_server_login Hook</h4>
<p>This hook allows for the insertion of code after login has successfully completed and just before the ticket creation.  One common use of this hook is to fill out the $_SESSION variable with site/user specific information.</p>
<h4>wpcas_server_auth_value Filter</h4>
<p>This filter (executed in a successful ticket validation in /cas/validate) is used to override the user identifier returned in the cas:authenticationSuccess XML response.  By default, the value returned is the $user_ID of the authenticated user.  Using this filter, that value can be altered to whatever suits your implementation.</p>


Alternatives to wpCAS Server

Top alternatives