Marcus Downing

Dani Llewellyn

Whenever a site is under development, or its content should remain private, you want to prevent to general public 
from reading it – whether deliberately or by accident.
A comman way to do this is with <a href="http://httpd.apache.org/docs/2.4/howto/auth.html" rel="nofollow ugc">HTTP authorisation</a>, 
but this has some problems:
<ul>
<li>Each user of your site has two different sets of username and password, one for the authorisation and one for 
WordPress login. It’s not uncommon for some users to find this confusing.</li>
<li>To set up authorisation you need access to your web server’s configuration (at least using the <code>.htaccess</code> file), 
which may not be available depending on your hosting supplier. 
You also need to learn how to configure the authorisation correctly, and risk breaking the site if you get it wrong.</li>
<li>When the time comes to remove the authorisation, you need to edit the configuration again.</li>
<li>In certain circumstances, combining authorisation with WordPress login can get a visitor into a circular redirect 
loop, where the result of logging in is to redirect to the login page.</li>
</ul>
Site PIN solves these problems by replacing authorisation with a simple PIN. This has the following advantages:
<ul>
<li>Everybody knows what a PIN is, and it’s clearly not the same as a password.</li>
<li>Logging into WordPress bypasses the PIN, so you can’t lock yourself out</li>
<li>It’s just a WordPress plugin, so no server configuration is necessary.</li>
<li>You can change or remove the PIN from WordPress admin.</li>
</ul>

Site PIN

Prevent careless visitors by locking your site down with a PIN

Alain-Aymerick FRANCOIS

vbonamy

If you’re happy with this plugin : 
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. 
My size is L. Best regards.
This Apereo CAS authentication plugin has no phpCas library dependency. This is not only an authentication plugin. 
You can build custom authorization rules according to cas user attributes populated. If user don’t exist in WordPress 
database, it can be created automatically. There are many features. You can customize everything.
<h4>Website</h4>
https://wpcassify.wordpress.com/
<h4>Development and release environment</h4>
This plugin is now developed and tested from a github repository. You can find it here : 
https://github.com/WP-Cassify/wp-cassify-develop
Don’t hesitate to contribute to this project. You can fork it and make pull requests !
<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>
Adding some customs hooks and filters.
</li>
<li>
Tested with Apereo CAS Server version 7.3.5
</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>
Be careful, to access to CAS User Attributes from your theme file (from 1.8.4), use code below :
<pre><code><?php
 if ( isset($GLOBALS['wp-cassify']) ) {
 print_r( $GLOBALS['wp-cassify']->wp_cassify_get_cas_user_datas() );
 }
?>
</code></pre>
</li>
<li>
Set up WordPress Roles to User according to CAS User attributes.
</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>
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) :
<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>
Receive email notifications when trigger is fired (after user account creation, after user login/logout).
</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>
Add ‘-IN’ and ‘-NOTIN’ operators to process array attributes values returned from CAS. 
When you have :
<pre><code>$cas_user_datas['title'] = array( 'Student', 'Professor' );
</code></pre>
</li>
</ul>
Then you can use :
<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.

Site PIN vs WP Cassify