Alain-Aymerick FRANCOIS

vbonamy

<p>If you’re happy with this plugin :<br />
As a reward for my efforts, I would like to receive T-shirts (or other goodies) as gifts from the universities or companies that use it.<br />
My size is L. Best regards.</p>
<p>This Apereo CAS authentication plugin has no phpCas library dependency. This is not only an authentication plugin.<br />
You can build custom authorization rules according to cas user attributes populated. If user don’t exist in WordPress<br />
database, it can be created automatically. There are many features. You can customize everything.</p>
<h4>Website</h4>
<p>https://wpcassify.wordpress.com/</p>
<h4>Development and release environment</h4>
<p>This plugin is now developed and tested from a github repository. You can find it here :<br />
https://github.com/WP-Cassify/wp-cassify-develop</p>
<p>Don’t hesitate to contribute to this project. You can fork it and make pull requests !</p>
<h4>Requirements</h4>
<ul>
<li>Require at least PHP version 7.0</li>
<li>Require at least PHP CURL package</li>
</ul>
<h4>Features included</h4>
<ul>
<li>SLO (Single Log Out) support (thanks to dedotombo and me)</li>
<li>Adding NCONTAINS operator (thanks to blandman)</li>
<li>Fix bug on Gateway mode (autologin) (thanks to dedotombo again). Now it’s now necessary to hack theme files to fire it.</li>
<li>Adding option logout on authentication failure to not disturb users</li>
<li>Initialize PHP session at a later stage (on wp_loaded not on init)</li>
<li>
<p>Adding some customs hooks and filters.</p>
</li>
<li>
<p>Tested with Apereo CAS Server version 7.3.5</p>
</li>
<li>Compatible with CAS Protocol version 2 and 3</li>
<li>Automatic user creation if not exist in WordPress database.</li>
<li>Synchronize WordPress User metas with CAS User attributes.</li>
<li>Add support for multivaluate cas user fields. Now multivaluate fields can be serialized to be stored in custom WP User meta.</li>
<li>Backup / Restore plugin configuration options settings</li>
<li>You can choose CAS User attributes you want to populate. Then you can access them via PHP Session.</li>
<li>
<p>Be careful, to access to CAS User Attributes from your theme file (from 1.8.4), use code below :</p>
<pre><code><?php
    if ( isset($GLOBALS['wp-cassify']) ) {
        print_r( $GLOBALS['wp-cassify']->wp_cassify_get_cas_user_datas() );
    }
?>
</code></pre>
</li>
<li>
<p>Set up WordPress Roles to User according to CAS User attributes.</p>
</li>
<li>If plugin is network activated, you can define User Role Rule scope by blog id.</li>
<li>Authorization rule editor.</li>
<li>Compatible with WordPress Access Control Plugin.</li>
<li>Manage URL White List to bypass CAS Authentication on certain pages.</li>
<li>
<p>Much simpler bypass authentication with post method provided by Susan Boland (See online documentation). Create wordpress authentication form with redirect attribute like this (works only if URL bypass is enabled in settings) :</p>
<pre><code><?php

    $args = array(
        'echo'           => true,
        'remember'       => true,
        'redirect' => site_url( '/?wp_cassify_bypass=bypass' ),
        'form_id'        => 'loginform',
        'id_username'    => 'user_login',
        'id_password'    => 'user_pass',
        'id_remember'    => 'rememberme',
        'id_submit'      => 'wp-submit',
        'label_username' => __( 'Username' ),
        'label_password' => __( 'Password' ),
        'label_remember' => __( 'Remember Me' ),
        'label_log_in'   => __( 'Log In' ),
        'value_username' => '',
        'value_remember' => false
    );

    wp_login_form( $args ); 
?>
</code></pre>
</li>
<li>
<p>Receive email notifications when trigger is fired (after user account creation, after user login/logout).</p>
</li>
<li>Define notifications rules based on user attributes values.</li>
<li>Purge user roles before applying user role rules.</li>
<li>Define user account expiration rules bases on CAS User attributes.</li>
<li>Network activation allowed</li>
<li>You can set Service Logout URL (Needs to have CAS Server with followServiceRedirects option configured).</li>
<li>Add support for web application hosted behind a reverse proxy. (Thanks to franck86)</li>
<li>Add custom hooks : wp_cassify_after_cas_authentication, wp_cassify_before_auth_user_wordpress, wp_cassify_before_redirect, wp_cassify_after_redirect. (See online documentation)</li>
<li>Custom filter to perform custom cas server response parsing. Hook name : wp_cassify_custom_parsing_cas_xml_response (See online documentation)</li>
<li>Custom shortcode to generate CAS login/logout link into your blog. (See online documentation)</li>
<li>Debug settings, dump last xml cas server response.</li>
<li>Detect if user has already authenticated by CAS from your public pages and perform auto-login with gateway mode</li>
<li>
<p>Add ‘-IN’ and ‘-NOTIN’ operators to process array attributes values returned from CAS.<br />
When you have :</p>
<pre><code>$cas_user_datas['title'] = array( 'Student', 'Professor' );
</code></pre>
</li>
</ul>
<p>Then you can use :</p>
<pre><code>    (CAS{title} -IN "professor")
</code></pre>


WP Cassify

The plugin is an Apereo CAS Client. It performs CAS authentication and autorization for Wordpress.

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>


wpCAS Server

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

WP Cassify vs wpCAS Server