An implementation of basic multi-factor authentication (MFA) for django projects
A simple implementation of basic Multi-Factor Authentication (MFA) functionality for Django applications.
The intent of this project is to:
- Provide basic yet effective MFA functionality for new and existing Django applications.
- Limit external (outside Django) dependencies wherever feasible.
- Simplify the setup and integration of MFA functionality in Django applications.
- Limit the amount of alteration required in existing codebases to integrate basic MFA functionality.
- Provide options to integrate more advanced or customized MFA functionality if desired.
At this time only email, phone call, and text message MFA options are supported. Future integrations (such as MS/Google Authenticator apps, OTP keys, WebAuthn, etc.) are possible.
Why It Exists
Upon evaluating various other Django MFA applications, most appeared to be one or more of the following:
- Their codebases were deprecated or unsupported.
- They often required a substantial amount of very specific dependenciesin order to even achieve basic functionality.
- The often required substantial changes to existing applications to function and integrate properly.
- Django >= version 3.0
- Django-Twilio (if using phone and/or text message MFA)
Twilio is the current integration for phone and text message MFA, but more are planned. Email MFA leverages the built-in Django email utilities.
Setup and Use
Download or clone the
simplemfa package here.
templates directory, create a new directory called 'simple_mfa' and in it place or create the following templates:
mfa/mfa_email.html(the MFA email message template)
mfa/mfa_text.html(the MFA text message template)
mfa/mfa_voice.html(plain text file with the message you want to send via phone call)
mfa/mfa_auth.html(the MFA login screen template)
mfa/mfa_base.html(the MFA base template)
path('mfa/', include('simplemfa.urls', namespace="simplemfa"))
REQUIRE_MFA = True(global setting which activates MFA for all users)
APP_NAME = "My App Name"(application name which is provided in the messages to the user)
DEFAULT_FROM_EMAIL = "my email@example.com"(the email address you want MFA messages to come from)
LOGIN_REDIRECT_URL = 'my_login_view_name'(the view users are sent to if they are not authenticated)
INSTALLED_APPS = [ ... 'simplemfa' ]
MIDDLEWARE = [ ... 'simplemfa.middleware.ValidateMFAMiddleware' ]
MFA_CODE_LENGTH(default is 6)
MFA_CODE_EXPIRATION(default is 900 seconds (15 minutes))
MFA_CODE_DELIVERY_DEFAULT(default is "EMAIL")
If using Twilio (for phone call or text message), you will need to install and set up djang-twilio according to the instructions for that package.
For email, ensure that your email is configured properly in your Django settings.
Once those items are complete, run
migrate for your project.
Run your project. It should allow you to access all public (login exempt) pages. After you log in, however, it will automatically redirect you to the MFA verification page where you will request and then enter an MFA code. If the code passes, you will be allowed to proceed as any normal authenticated user would in your application.
A project example is coming shortly.
As of right now, MFA is applied globablly in the
settings.py file. We are working on changing that to track in a User's settings as part of an
MFAProfile model attached to the User object.
MFA codes sent to users are stored as one-way hashed objects using Django's built-in hashers. It is treated as a password field in the application. The hashes are created and verified using Django's own
check_password() functions, respectively. The ONLY time a plain-text MFA code is created in the application is during the sending of the user message to the Twilio API or via email. At no other time are MFA codes rendered or stored as plain text. All MFA codes are destroyed immediately after use or upon expiration (
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for django_simplemfa-0.1-py3-none-any.whl