BinaryCarpenter

<p>This plugin let you enable face login without using password. Thus, you don’t have to worry about keyloggers stealing your password.</p>
<h3>Why using face authentication for WordPress login?</h3>
<p>WordPress has grown so much since its beginning. People use WordPress for various purposes including building a store, create API and of course blogging. With its popularity comes hackers, attackers, phishers…<br />
Those bad guys do everything to break into your site and steal your information, including your business.</p>
<h3>How to prevent hackers from break into your site?</h3>
<p>There are various ways to get access to the admin of a website. However, the most common way is to hack the username and password. It may surprise you but many people still weak password nowadays. Passwords that contain only numbers, words are in dictionary … are the easiest to hack.<br />
The solution would be using a strong password which is impossible to remember.</p>
<p>However, you still have to store that password somewhere. Maybe in a text file.</p>
<p>When you open the text file to copy the password, someone can steal your password by simply peek at your computer or use a recording device.</p>
<h3>Using passwords is prone to hacks, what’s the fix</h3>
<p>If you say that using password is a risk, you are completely right. No matter how strong a password is, it can be stolen. But, what’s the alternative?</p>
<h3>Introducing to password-less login for WordPress</h3>
<p>The answer to the risk we mentioned is to stop using password completely. For real.</p>
<p>But you may wonder, how can you use password-less login on WordPress?</p>
<p>It’s simpler that you think. With today’s technology, there are smarter, more secure ways to verify one’s identity.</p>
<p>You have known fingerprints. Now we have face.</p>
<p>Imagine you can login to your site the same way you open your phone.</p>
<h3>How is this secure? Meet two-factor login</h3>
<p>If you door has only one lock, thieves have good chance to break into your house.<br />
But if you have two locks, their chances drop drastically.<br />
That’s the same theory of two factor login.<br />
The one that requests to access your site (maybe you) have to complete two challenges.<br />
Currently, many people use password for phase one and a simple token for later.<br />
But we have discussed the inconvenience of using password, also the risks.<br />
So, why don’t we treat ourselves a bit kinder by using something easy for us at both phases?</p>
<h3>Using two factor face authentication to login into your WordPress site</h3>
<p>Let’s imagine this, you go to your WordPress login page, instead of typing in the password, you only look at the camera.<br />
The site recogizes you as its owner. It wouldn’t let you in yet. There is a chance that someone uses a statue to fake your identity.<br />
Instead, it will send you a token (4 to 8 digits) to your prefered devices (Email, Authenticator app).</p>
<p>You then send the token to the site. If you provide the correct token, you are now login.</p>
<p>As you can see, it is almost impossible for attackers to impersonate anywhere in the whole process.</p>


WP Face Login – Face Authentication For WordPress

great

Enable face authentication login with ease

apokalyptik

Stephane Daury (stephdau)

Paul Gilzow

<p>Please see the Changelog (Development tab above) for recent updates/changes.</p>
<p>wpDirAuth shifts authentication from the local WordPress instance to a central directory (LDAP) server(s).</p>
<p>wpDirAuth allows users of central directory (LDAP) servers to login to authorized WordPress instances without having to register. The plugin creates a new account for each directory user on first login so that they have full access to preferences and functions, as any WP user would. Activating the plugin will not restrict you to using directory authentication and you will still be able to both create new WP-only users as well as turn on public registration in WordPress. You can also assign any privilege levels to your directory users, and the those users will be referred to their institutional password policy whenever they would normally able to update their WP passwords (on the profile screen, in user edit, etc).</p>
<h4>LDAP/LDAPS</h4>
<p>Authentication should work with most LDAP enabled directory services, such as OpenLDAP, Apache Directory, Microsoft Active Directory, Novell eDirectory, Sun Java System Directory Server, and more. wpDirAuth supports LDAP and LDAPS (SSL) connectivity and can force SSL for WordPress authentication if it is available on the Web server. It also supports server connection pools, for pseudo load balancing and fault tolerance, or multiple source directory authentication. Because the key used to locate a user’s profile in the LDAP server is not always the same, depending on your LDAP server type and institutional choices, you can define your own through the wpDirAuth administration tool. When logging in as a directory user, the WP “remember me” feature is downgraded from 6 months for regular WP users to only 1 hour, so that institutional passwords are not overly endangered when accessing WP from public terminals.</p>
<h4>Branding & Notifications</h4>
<p>You can define notifications addressed to your directory users in key WordPress areas, such as the login screen and the profile edit screen. Since these admin-editable values support HTML (admin, coders, beware of xss!), you can point your directory users to central support information related to functions such as changing their institutional password, a WordPress usage related policy, etc. There is also a simple and optional terms of services concept, only implemented for directory users, which will simply record a one-time acceptance date when agreed upon. Note that agreeing to the TOS has no effect on the user’s level of access in the system, fact which could change in future version if there is a demand for it, or through direct code contribution to that effect.</p>
<h3>Using wpDirAuth</h3>
<p>Once installed and activated, you will be able to administer your directory settings through the dedicated plugin configuration tool found under the <code>wpDirAuth</code> menu found in the WordPress <code>Settings</code> admin section. Directory Authenticated users can now be pre-added to your wordpress system and granted roles by going to the <code>Add Dir Auth User</code> menu found in the WordPress <code>Users</code> admin section. Contextual help for this section is available for this section within WordPress’ built-in help menu. See the inline help found in the tool for more information on the settings. There is a secondary activation toggle, so you can install and activate the plugin, check out the options panel, but not immediately accept directory authentication, or even simply turn the feature on or off at any time.</p>
<h3>Help and Support</h3>
<p>Please post questions, request for help to the WordPress plugins forum or email <a href="mailto:wpdirauth@gilzow.com" rel="nofollow ugc">wpdirauth@gilzow.com</a>. Please be sure to include ‘wpdirauth’ in the subject line.</p>
<h3>TO-DO’s</h3>
<ul>
<li>Internationalization</li>
<li>Refactor to a class</li>
<li>More action/filter hooks</li>
</ul>
<h3>Source and Development</h3>
<p>wpDirAuth welcomes friendly contributors wanting to lend a hand, be it in the form of code through SVN patches, user support, platform portability testing, security consulting, localization help, etc. The [current] goal is to keep the plugin self-contained (ie: no 3rd-party lib) for easier security maintenance, while keeping the code clean and extensible. Focus is on security, features, security, and let’s not forget, security. Unit tests will hopefully be developed and constant security audit performed. Recurring quality patch contributions will lead to commit privileges to the project source repository. Please post questions/requests for help to the wordpress forums and/or email <a href="mailto:wpdirauth@gilzow.com" rel="nofollow ugc">wpdirauth@gilzow.com</a></p>
<h3>License</h3>
<p><a href="http://www.gnu.org/licenses/gpl.html" rel="nofollow ugc">General Public License</a><br />
Copyrights are listed in chronological order, by contributions.<br />
wpDirAuth: WordPress Directory Authentication, original author<br />
Copyright (c) 2007 Stephane Daury – http://stephane.daury.org/<br />
wpDirAuth and wpLDAP Patch Contributions<br />
Copyright (c) 2007 PKR Internet, LLC – http://www.pkrinternet.com/</p>
<p>wpDirAuth Patch Contributions<br />
Copyright (c) 2007 Todd Beverly<br />
wpLDAP: WordPress LDAP Authentication<br />
Copyright (c) 2007 Ashay Suresh Manjure – http://ashay.org/<br />
wpDirAuth Patch Contribution and current maintainer<br />
Copyright (c) 2010-2017 Paul Gilzow – http://gilzow.com/<br />
wpDirAuth is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.<br />
wpDirAuth is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br />
You should have received a copy of the GNU General Public License along with this program. If not, see <a href="http://www.gnu.org/licenses/" rel="nofollow ugc">http://www.gnu.org/licenses/</a>.</p>
<h3>Project History</h3>
<p>Originally started from a patched version of wpLDAP (1.02+patch), wpDirAuth has<br />
since then been heavily overhauled and features have been modified and added.<br />
In other words, a classic case of <code>pimp my lib'</code> (hopefully for the better).<br />
* Current: wpDirAuth: <a href="http://wpdirauth.gilzow.com/" rel="nofollow ugc">http://wpdirauth.gilzow.com/</a><br />
* Original: wpLDAP: <a href="https://wordpress.org/plugins/wpldap/" rel="ugc">https://wordpress.org/plugins/wpldap/</a><br />
* wpLDAP Patch: <a href="https://web.archive.org/web/20100731020249/http://www.pkrinternet.com/~rbulling/private/wpLDAP-1.02-ssl.patch" rel="nofollow ugc">https://web.archive.org/web/20100731020249/http://www.pkrinternet.com/~rbulling/private/wpLDAP-1.02-ssl.patch</a></p>


wpDirAuth

WordPress directory authentication plugin through LDAP and LDAPS (SSL).

WP Face Login – Face Authentication For WordPress vs wpDirAuth