Paul Ryan

jojaba

the_elusive

Anil Natha

pkarjala

Eduardo Larequi

Authorizer restricts access to a WordPress site to specific users, typically students enrolled in a university course. It maintains a list of approved users that you can edit to determine who has access. It also replaces the default WordPress login/authorization system with one relying on an external server, such as Google, CAS, LDAP, or an OAuth2 provider. Finally, Authorizer lets you limit invalid login attempts to prevent bots from compromising your users’ accounts.
View or contribute to the plugin source on GitHub: <a href="https://github.com/uhm-coe/authorizer" rel="nofollow ugc">https://github.com/uhm-coe/authorizer</a>
Authorizer requires the following:
<ul>
<li>CAS server (2.x, 3.x, 4.x, 5.x, 6.x, or 7.x) or LDAP server (plugin needs the URL)</li>
<li>PHP extensions: php-ldap, php-curl, php-dom</li>
</ul>
Authorizer provides the following options:
<ul>
<li>Authentication: WordPress accounts; Google accounts; CAS accounts; LDAP accounts; OAuth2 accounts</li>
<li>Login Access: All authenticated users (all local and all external can log in); Only specific users (all local and approved external users can log in)</li>
<li>View Access: Everyone (open access); Only logged in users</li>
<li>Limit Login Attempts: Progressively increase the amount of time required between invalid login attempts.</li>
<li>Shortcode: Use the <code>[authorizer_login_form]</code> shortcode to embed a wp_login_form() outside of wp-login.php.</li>
</ul>

Authorizer

Integrates nicely with Google hosted domain/s. Couldn't be happier with how it works!

Integrates well with Google Logins

I've experimented this plugin on a multisite and everything works pretty well.

Works great even on a multisite setup

Authorizer limits login attempts, restricts access to specific users, and authenticates against external sources (OAuth2, Google, LDAP, or CAS).

sojweb

THIS IS FOR DEVELOPMENT PURPOSES, NOT FOR USE ON PRODUCTION SITES
This plugin is meant to be a reference; I’ve talked to several people who have similar setups, and thought it would beneficial to share some code.
This plugin allows users to be authenticated via CAS, and logins to be controlled via LDAP. Default user roles can be assigned based on LDAP group membership, and accounts can be auto-created for users that exist in LDAP, but not yet in WordPress.
It assumes that, for CAS authentication, the user is redirected to an outside address, then back to the referring address; that’s how it works where I’m at :-). You can also specify a group in LDAP that will always have admin privileges; useful for tech staff.
Before the plugin is used, the constants in <code>soj-ldap_constants.inc.php</code> must be filled out. The CAS default password is the one the user is registered with in WordPress; so all WP users will have this password. Be aware of that. There is obviously more that could be done there, and I’m happy to work with others who have ideas.
I’ve adapted this from an in-house plugin I made, so there might be leftover code bits or things that look strange… feel free to harass me about that, I did this in a bit of a rush.
I’ve only ever used this plugin on one environment, so it might not work out-of-the-box for you. I’m interested in making this plugin more robust, however, so please let me know of any issues.
Contact me: jj56@indiana.edu

SoJ CAS/LDAP Login

This plugin allows users to be authenticated via CAS, and logins to be controlled via LDAP.

Authorizer vs SoJ CAS/LDAP Login