Fortytwo

<h4>What is Two-factor Authentication?</h4>
Authentication – the process of verifying your identity – boils down to one of three simple elements:
<ul>
<li>Something the user knows (PIN, password)</li>
<li>Something the user owns (mobile phone, device)</li>
<li>Something the user is (biometric, retina, fingerprint)</li>
</ul>
<a href="https://www.fortytwo.com/solutions/two-factor-authentication/" rel="nofollow ugc">Two-factor Authentication</a> (2FA) is a combination of any two of these unique identifiers.
<h4>How does our 2FA plugin work?</h4>
With <a href="https://www.fortytwo.com" rel="nofollow ugc">Fortytwo</a>’s 2FA WordPress plugin, the user only requires the username and password to login to their site (as per any standard login sequence) and a mobile phone to receive the one-time authentication code via SMS.
Our plugin is fully customisable and can be adapted to meet your specific needs, for example, you can assign 2FA to certain users depending on their specific administrative roles in WordPress and disable 2FA for users when they are using a known or ‘trusted’ device for a specific period of time. Fortytwo’s WordPress 2FA plugin offers the unique advantage of providing a highly customisable authentication process for users and provides an additional level of security when and as required.
<h4>What features does it include?</h4>
Fortytwo’s WordPress plugin comes with a myriad of features including the option to:
<ul>
<li>activate or disable 2FA for registration and/or login allowing the user to login using a username, password and 2FA or just a username and password</li>
<li>activate 2FA for login according to the user’s role in WordPress, for example, you can disable 2FA for certain users such as subscribers while maintaining 2FA for users with critical roles</li>
<li>Activate 2FA as optional or mandatory option for users, so you can give to your user the option to activate 2FA or force the option by default.</li>
<li>assign ‘trusted’ devices to specific users allowing the user – after their initial 2FA login – to validate their devices as ‘trusted’ for a specific time period, assigned by them in the settings. This option ensures that users aren’t required to enter an authentication code repeatedly with an assigned trusted device, after the initial 2FA login</li>
<li>resend the authentication code after registration if the SMS was not received – this allows the user to request the authentication code after 60 seconds and/or change his phone number in the event that an incorrect phone number was submitted</li>
<li>resend the authentication code after login if the SMS was not received – this allows the user to request the authentication code again after 60 seconds – this re-send option can also be disabled in the settings</li>
<li>to customize the behavior of the 2FA as <a href="https://www.fortytwo.com/apis/two-factor-authentication/" rel="nofollow ugc">documented on the API</a> including changes to the authentication code length and type (numeric, alpha or alphanumeric), case sensitive validation, options to log a response via a callback URL and customise sender ID ‘s visible to the users</li>
</ul>
Fortytwo’s 2FA WordPress plugin supports 2FA for all Smart phones (iPhone, Android, BlackBerry), as well as basic phones.
<h4>Why use Fortytwo’s WordPress plugin?</h4>
<ul>
<li>Security Incorporating 2FA in to the user login process, creates a level of protection and security for your WordPress site that complex passwords can no longer guarantee</li>
<li>Customised functionality This is our first version of the plugin and we’re keenly interested in your feedback.</li>
</ul>
If there is additional functionality that you would you like to see, please let us know – we are happy to work on developing features to meet your specific requirements and endeavor to implement this in as short a time-frame as possible.
<h3>Configuration</h3>
Once the plugin is activated you have to configure the plugin before use:
<ol>
<li>In the admin panel go to Settings > Two Factor Authentication</li>
<li>Enter the token you have from the <a href="https://controlpanel.fortytwo.com/" rel="nofollow ugc">fortytwo control panel</a></li>
<li>Configure the other options accordingly to your needs</li>
<li>push the save button</li>
</ol>
Note: The Two factor authentication works only for the users who have the 2FA phone number on their profile.
<h3>Version 1.1.1</h3>
2016-12-22 
* [IMPROVEMENT] Support for WordPress 4.6.X. 
* [IMPROVEMENT] Don’t call login_header if the function was disabled.
<h3>Version 1.1.0</h3>
2016-10-04 
* [IMPROVEMENT] Support for WordPress 4.6.X. 
* [IMPROVEMENT] Update SDK dependencies. 
* [IMPROVEMENT] Phone field rendering updated. 
* [IMPROVEMENT] New API Paremeter : Message template to personalize the message sent with the 2FA Code. 
* [IMPROVEMENT] New Mandatory option allowing to have 2FA option as optional or mandatory on login and/or on register.
<h3>Version 1.0.8</h3>
2016-05-02 
* [DOCUMENTATION] Fix typo in the readme file.
<ul>
<li>[DOCUMENTATION] Fix typo in the readme file.</li>
</ul>
<h4>Version 1.0.7</h4>
2016-05-02 
* [BUG] Update publish script to properly track/add new files and directory and untrack/delete deleted files. 
* [BUG] Clean the SVN tree.
<ul>
<li>[BUG] Update publish script to properly track/add new files and directory and untrack/delete deleted files.</li>
<li>[BUG] Clean the SVN tree.</li>
</ul>
<h4>Version 1.0.6</h4>
2016-04-28 
* [BUG] Settings – Update “API Sensitive case” field ID. 
* [DOCUMENTATION] Change “why” items to list.
<ul>
<li>[BUG] Settings – Update “API Sensitive case” field ID.</li>
<li>[DOCUMENTATION] Change “why” items to list.</li>
</ul>
<h4>Version 1.0.5</h4>
2016-04-26 
* [IMPROVEMENT] Update contributor id
<ul>
<li>[IMPROVEMENT] Update contributor id</li>
</ul>
<h4>Version 1.0.4</h4>
2016-04-25 
* [IMPROVEMENT] Support for WordPress 4.5
<ul>
<li>[IMPROVEMENT] Support for WordPress 4.5</li>
</ul>
<h4>Version 1.0.3</h4>
2016-04-25 
* [DOCUMENTATION] Add some tags on the presentation of the plugin. 
* [DOCUMENTATION] Update the screenshots. 
* [DOCUMENTATION] Update readme.txt description.
<ul>
<li>[DOCUMENTATION] Add some tags on the presentation of the plugin.</li>
<li>[DOCUMENTATION] Update the screenshots.</li>
<li>[DOCUMENTATION] Update readme.txt description.</li>
</ul>
<h4>Version 1.0.2</h4>
2016-04-20 
* [DOCUMENTATION] Fix header description to feet in 150 characters
<ul>
<li>[DOCUMENTATION] Fix header description to feet in 150 characters</li>
</ul>
<h4>Version 1.0.1</h4>
2016-04-20 
* [DOCUMENTATION] Update the readme.txt
<ul>
<li>[DOCUMENTATION] Update the readme.txt</li>
</ul>
<h4>Version 1.0.0</h4>
2016-04-19 
* First stable version.
<ul>
<li>First stable version.</li>
</ul>
<h4>Version 1.0.0-RC11</h4>
2016-04-19 
* [BUG] Fix error message when invalid token used. 
* [BUG] Fix a typo. 
* [IMPROVEMENT] Update readme.txt
<ul>
<li>[BUG] Fix error message when invalid token used.</li>
<li>[BUG] Fix a typo.</li>
<li>[IMPROVEMENT] Update readme.txt</li>
</ul>
<h4>Version 1.0.0-RC10</h4>
2016-04-18 
* [BUG] Fix phone number validation on register. 
* [BUG] Fix various typos. 
* [BUG] Fix code validation on register/login 
* [BUG] Fix bug when we validate code after a fail on register. 
* [BUG] Fix inconsistency on naming of authentication code.
<ul>
<li>[BUG] Fix phone number validation on register.</li>
<li>[BUG] Fix various typos.</li>
<li>[BUG] Fix code validation on register/login</li>
<li>[BUG] Fix bug when we validate code after a fail on register.</li>
<li>[BUG] Fix inconsistency on naming of authentication code.</li>
</ul>
<h4>Version 1.0.0-RC9</h4>
2016-04-14 
* [BUG] Device was always setup as trusted. 
* [BUG] Fix missing phone helper on edit user. 
* [BUG] Fix nullable callbackurl. 
* [BUG] Fix validation code after one fail. 
* [BUG] Fix resend option on login.
<ul>
<li>[BUG] Device was always setup as trusted.</li>
<li>[BUG] Fix missing phone helper on edit user.</li>
<li>[BUG] Fix nullable callbackurl.</li>
<li>[BUG] Fix validation code after one fail.</li>
<li>[BUG] Fix resend option on login.</li>
</ul>
<h4>Version 1.0.0-RC8</h4>
2016-04-12 
* [BUG] Add missing jquery dependency on login 
* [BUG] Fix Trusted device Activate/Disabled option 
* [BUG] Fix naming convention for Authentication code 
* [IMPROVEMENT] Update in code documentation 
* [IMPROVEMENT] Adding field validation in the settings 
* [BUG] Fix missing dependency * Jquery 
* [BUG] Fix a typo on setting panel. 
* [BUG] Fix a bug with the cookie path.
<ul>
<li>[BUG] Add missing jquery dependency on login</li>
<li>[BUG] Fix Trusted device Activate/Disabled option</li>
<li>[BUG] Fix naming convention for Authentication code</li>
<li>[IMPROVEMENT] Update in code documentation</li>
<li>[IMPROVEMENT] Adding field validation in the settings</li>
<li>[BUG] Fix missing dependency – Jquery</li>
<li>[BUG] Fix a typo on setting panel.</li>
<li>[BUG] Fix a bug with the cookie path.</li>
</ul>
<h4>Version 1.0.0-RC7</h4>
2016-04-06 
* [BUG] Resend SMS no showing on login. 
* [BUG] Disable 2FA on register not working properly.
<ul>
<li>[BUG] Resend SMS no showing on login.</li>
<li>[BUG] Disable 2FA on register not working properly.</li>
</ul>
<h4>Version 1.0.0-RC6</h4>
2016-04-06 
* [IMPROVEMENTS] Updating versions numbers
<ul>
<li>[IMPROVEMENTS] Updating versions numbers</li>
</ul>
<h4>Version 1.0.0-RC5</h4>
2016-04-04 
* [IMPROVEMENTS] Small fixes
<ul>
<li>[IMPROVEMENTS] Small fixes</li>
</ul>
<h4>Version 1.0.0-RC4</h4>
2016-04-04 
* [IMPROVEMENTS] Fixing various bugs 
* [IMPROVEMENTS] Adding screenshots for the wordpress plugin website
<ul>
<li>[IMPROVEMENTS] Fixing various bugs</li>
<li>[IMPROVEMENTS] Adding screenshots for the wordpress plugin website</li>
</ul>
<h4>Version 1.0.0-RC3</h4>
2016-04-01 
* [IMPROVEMENTS] Adding assets : banner and icons.
<ul>
<li>[IMPROVEMENTS] Adding assets : banner and icons.</li>
</ul>
<h4>Version 1.0.0-RC2</h4>
2016-03-30 
* [IMPROVEMENTS] Update assets for WordPress publication 
* [IMPROVEMENTS] Add publish.sh file for publishing version on the SVN repo.
<ul>
<li>[IMPROVEMENTS] Update assets for WordPress publication</li>
<li>[IMPROVEMENTS] Add publish.sh file for publishing version on the SVN repo.</li>
</ul>
<h4>Version 1.0.0-RC1</h4>
2016-03-24 
* [IMPROVEMENTS] : Add Readme.txt for wordpress repo and the icon image. 
* [IMPROVEMENTS] : Updating documentation. 
* [FEATURES] : Initial features.
<ul>
<li>[IMPROVEMENTS] : Add Readme.txt for wordpress repo and the icon image.</li>
<li>[IMPROVEMENTS] : Updating documentation.</li>
<li>[FEATURES] : Initial features.</li>
</ul>

Fortytwo – Two-Factor Authentication

Fortytwo’s 2FA plugin controls access to your site by sending an authentication code via SMS to your mobile phone when you register or login.

This plugin activates easy self-service two-factor (or multi-factor) authentication logins for you and all your users.
CryptoPhoto is the world’s easiest-to-use, fastest, and most secure two-factor (and optionally multi-factor) authentication. Logins are usually as fast and easy as “one tap”, and no training is needed.
After installation, users will see a new “CryptoPhoto” dashboard menu item, which they can use themselves to activate and download printable tokens, or install the CryptoPhoto app to connect their smartphones or tablets (iOS, Android, WindowsPhone, and Blackberry).
Our user-experience testing was conducted using year-1 schoolchildren. They all successfully logged in without us giving them any instructions. CryptoPhoto is way easier to use, than it is to describe – but here’s how it works anyway:
After users activate CryptoPhoto, they will see a photo during their logins, and at the same time, their phone (or tablet) will beep and show them a collection of photos too. (if they don’t have any smart devices, or have lost their phone, they use their downloaded paper token instead). To complete their login, they simply tap the one on their phone that matches the login one (or type the codes if they don’t have a phone, or don’t have mobile coverage). This is why CryptoPhoto is currently the worlds most secure two-factor-authentication – the photos create “mutual authentication” (which blocks phishing and Man-in-the-middle MitM attacks) – nobody else does this.
CryptoPhoto also combats malware, viruses, advanced-persistent-threats (APT’s), trojans, keyloggers, phishing and spoof/impostor/fake websites, vishing (telephone phishing), shoulder-surfing attacks, careless password choices by end users, password re-use problems (eg: passwords stolen from other web sites won’t compromise CryptoPhoto users), confidence tricks, and more: we simultaneously protect our users against more threats than any competing solution (and, in fact, against more threats than all competing solutions combined).
CryptoPhoto works with or without smartphones/tablets, works home and abroad, online and offline, and keeps working (securely) even when users loose their phones/tablets. CryptoPhoto is the industries lowest-support-required two-factor-authentication solution: you do not need to hire a support team to mange users enrollments and issues (like bypasses and re-enrollment when users loose their phones/tokens).
To securely install the CryptoPhoto plugin, you will have to follow some steps to generate unique keys for your installation etc. The steps are on in our <a href="https://cryptophoto.com/info/admin" rel="nofollow ugc">Cryptophoto Installation guide</a> if you need help, or have comments/suggestions/criticism, please email us or visit <a href="https://cryptophoto.com/help" rel="nofollow ugc">CryptoPhoto Support page</a>, or feel free to call any time on skype:chrisdrake if you want one-to-one help with anything.
For more information, please visit the <a href="http://cryptophoto.com" rel="nofollow ugc">CryptoPhoto site</a>

CryptoPhoto

This plugin activates easy self-service two-factor (or multi-factor) authentication logins for you and all your users.

Fortytwo – Two-Factor Authentication vs CryptoPhoto