Home
This extension helps you to provide a more modern form of authenticating users on your DNN website. Instead of using the archaic username and password method of logging in, it instead relies on the authentication security provided by the email provider of choice by the end end-user.
When they attempt to log in, they'll be sent an email, where they'll need to copy the code in their email, then paste it into the login form. If the code is correct, then they'll be logged in.
In the interest of keeping things tidy, codes are automatically cleared out as they expire, and after 5 subsequent failed attempts, end-users must wait an hour before they can try again.
How do you say "Easy Security" without saying "easy security?" Oh, never mind. 😎
Yes, it's not real code. It's just supposed to be fun. :P
This solution is created and maintained by Upendo Ventures for the DNN CMS Community. Please consider sponsoring us for this and the many other open-source efforts we do. It's a lot. :)
- Sponsor Us (we're grateful at any level 🙏🏽)
This authentication provider installs the same way as any other extension in DNN.
This authentication provider upgrades the same way as any other extension in DNN.
Once installed, all you need to do is navigate to the website as a superuser.
Next, use the persona bar to find the Security view in the Manage menu.
You'll now see the Upendo Simple Auth provider listed as an option for the Default Authentication Provider field.
Select the Upendo Simple Auth option, and save your changes.
That's it! The very next page load will have your end users now using this new method of authenticating.
End-users will now have a streamlined user experience when logging in. Here's there new workflow:
- Visit the site.
- Choose to login.
- When viewing the form, they enter their username, then click the
Send Codelink. - An email is generated and sent to the email address for that user account, if it exists.
- The end-user copies the code from their email, and pastes it into the login form.
- Click to log in.
That's it! They're logged in, as long as the code is accurate.
End-users that try unsuccessfully 3-times in a row will become locked out of the login form for 1-hour.
In the future, the plan is to implement a user management view of some kind to help you manage this feature.
In the meantime, you can do either:
- Tell the end-user to wait until the timeout expires.
- Find the user record in the
Upendo_SimpleAuthVerificationtable by their username and delete it. Then, clear cache.
The emails generated have a template that includes tokens.