gpaterno

A lot of web sites, even well known ones (newspapers, telcos, …) adopts 
WordPress as their CMS. WordPress is a great platform, however it 
can happen that password leaking or guessing might lead to unauthorized 
access to the platform. A potential attacker can be therefore able to 
change articles, part of the web site and/or make the website unavailable, 
with image and economic damages for a company or for a blogger. 
This is even more true if your website is not SSL protected.
SecurePass is a SaaS service offering an easy and affordable solution 
for One Time Passwords (OTP) and strong authentication in general. They 
offer 5 users for free included with their standard (=basic) account, which 
is more than enough for standard blogs and web sites. Companies can purchase 
additional users, if needed.
More information on the section “Setup and configure SecurePass” in Other Notes. 
To open a SecurePass account go to http://www.secure-pass.net/open
<h3>Setup and configure SecurePass</h3>
If you don’t own already an account with SecurePass, you can sign-up for a new account here: http://www.secure-pass.net/open
Note: Use “misec2011” as promo code, it will give you an entitlement for using 
SecurePass up to 10 users for 2 years free-of-charge. Without any promo code, 
you will have 5 users for 20 years for free. It depends on what you need (more users or more years).
Connect to the admin interface on https://admin.secure-pass.net 
and create a new device (basically a RADIUS client).
In the admin interface, go to the “Device” section and add a new device. 
You will need to set the public IP Address of the server, a fully qualified 
domain name (FQDN), and the secret password for the radius authentication. 
It’s ok if your web server is behind a firewall and/or NAT, ensure that 
your server has rights to send (and receive) RADIUS authentication requests, 
i.e. UDP port 1812.
<h3>Further reading</h3>
<ul>
<li>
This plugin web site: 
https://github.com/gpaterno/wp-securepass/
</li>
<li>
SecurePass web site: 
http://www.secure-pass.net/
</li>
<li>
UK on-line shop for SecurePass (they sell hardware tokens): 
http://shop.nervinesecurity.com/
</li>
</ul>

SecurePass authentication

This is a plugin to autheticate users through the SecurePass One Time Passwords service.

Hamid Alinia

Enable OTP login for WordPress that supports WooCommerce using phone numbers, SMS, or WhatsApp. Secure passwordless login with custom gateways and GDPR compliance.
Login/register with phone number in WordPress can happen with this plugin. Your customer can authenticate with their mobile number via OTP.
Added country flags to login with phone number form
You can add almost every SMS gateways (if you have) yourself for free, or you can ask us to develop your sms gateway with paying extra.
you can change style and appearance of forms
You can use Firebase, textlocal and other SMS gateways
For checking docs and getting more help please visit: 
<a href="https://idehweb.com/product/login-with-phone-number-in-wordpress/" title="login with phone number in WordPress" rel="nofollow ugc">Login with phone number in WordPress documentations</a>
<ul>
<li>
Login with phone number in WordPress
</li>
<li>
Login with OTP WordPress
</li>
<li>
Login with mobile number WordPress
</li>
<li>
Login/Register with E-mail
</li>
<li>
WordPress Login Form
</li>
<li>
Woocommerce Registration Form
</li>
<li>
Woocommerce Login With Phone Number
</li>
<li>
WordPress OTP Login
</li>
<li>
Woocommerce Registration With Phone Number
</li>
<li>
Add Phone Number to WordPress Registration
</li>
<li>
Simple Use
</li>
<li>
Support of International SMS Delivery
</li>
<li>
Activating Users by Phone Number
</li>
<li>
Password Recovery Form
</li>
<li>
Page Authentication in Order to Visit Pages
</li>
<li>
Login and Registration with Phone Number
</li>
<li>
Redirect Users to Specific URLs After Logging in or Registering
</li>
</ul>
You can use your custom gateway. you can also use other ready sms gateways from idehweb.com.
Supported gateways for now:
<ul>
<li>Firebase – Free</li>
<li>Msg91 – Free</li>
<li>Twilio</li>
<li>Netgsm</li>
<li>Alibabacloud</li>
<li>Messagebird</li>
<li>Kavenegar</li>
<li>Trustsignal</li>
<li>taqnyat</li>
<li>2factor</li>
<li>Textlocal</li>
<li>BlueSoft</li>
<li>IQSMS</li>
<li>Whatsapp</li>
<li>Ultramessage</li>
<li>Telegram</li>
<li>Ippanel</li>
<li>Sms.ir</li>
<li>MelliPayamak</li>
<li>Farazsms</li>
</ul>
You can now choose to store phone numbers with or without the country code.
<iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/0B0sE9JMzCE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe>
<h3>External Services</h3>
This plugin uses external services to provide chat support and analyze user behavior. Below is the list of services used and what data is sent:
<ol>
<li>Crisp Chat</li>
</ol>
– Used to provide live chat functionality within the plugin for user support. 
– Data sent: user chat messages, name, email, IP address. 
– Service provider: Crisp IM SARL 
– Terms of Service: https://crisp.chat/en/terms/ 
– Privacy Policy: https://crisp.chat/en/privacy/
<ol>
<li>Microsoft Clarity</li>
</ol>
– Used for user behavior analytics to understand how users interact with the plugin’s administrative pages. 
– Data sent: user interactions like mouse movements, clicks, and scrolling. Personally identifiable information (PII) is masked. 
– Service provider: Microsoft 
– Terms of Service: https://clarity.microsoft.com/terms 
– Privacy Policy: https://privacy.microsoft.com/en-us/privacystatement
<ol>
<li>Firebase Authentication</li>
</ol>
– Used to verify users’ phone numbers with OTP for secure authentication. 
– Data sent: phone number and verification requests. IP addresses are used for security and abuse prevention. 
– Service provider: Google Firebase 
– Terms of Service: https://firebase.google.com/terms 
– Privacy Policy: https://firebase.google.com/support/privacy

OTP Login With Phone Number, OTP Verification

1. Shows ads.
2. Shows developers real face in my admin dashboard :|
3. The core basic functionality (connection to KaveNegar SMS service provider) is locked behind Pro version. Almost all SMS gateways are locked behind a paywall.
4. "Enable usage tracking" option checked by default (without users knowladge).

Shows Ads and Needs Pro Version!

OTP login with phone, SMS, or WhatsApp. OTP verification for WordPress & WooCommerce using custom gateways. GDPR-compliant. Login with otp

SecurePass authentication vs OTP Login With Phone Number, OTP Verification