Skip to main content

This Django app adds two factor authentication to Wagtail. Behind the scenes it use django-otp which supports Time-based One-Time Passwords (TOTP). This allows you to use various apps like Authy, Google Authenticator, or 1Password.

All credits go to the original developer/s, I have just made newer release of the package that support Wagtail >= 6.0.

You can checkout the original repo here

Installation

pip install wagtail-2fa-new

Then add the following lines to the INSTALLED_APPS list in your Django settings:

INSTALLED_APPS = [
    # ...
    'wagtail_2fa',
    'django_otp',
    'django_otp.plugins.otp_totp',
    # ...
]

Next add the required middleware to the MIDDLEWARE. It should come after the AuthenticationMiddleware:

MIDDLEWARE = [
    # .. other middleware
    # 'django.contrib.auth.middleware.AuthenticationMiddleware',

    'wagtail_2fa.middleware.VerifyUserMiddleware',

    # 'wagtail.core.middleware.SiteMiddleware',
    # .. other middleware
]

Migrate your database:

python manage.py migrate

Settings

The following settings are available (Set via your Django settings):

  • WAGTAIL_2FA_REQUIRED (default False): When set to True all staff, superuser and other users with access to the Wagtail Admin site are forced to login using two factor authentication.

  • WAGTAIL_2FA_OTP_TOTP_NAME (default: False): The issuer name to identify which site is which in your authenticator app. If not set and WAGTAIL_SITE_NAME is defined it uses this. sets OTP_TOTP_ISSUER under the hood.

Making 2FA optional

With the default VerifyUserMiddleware middleware, 2FA is enabled for every user. To make 2FA optional, use the VerifyUserPermissionsMiddleware middleware instead.

To do so, use the VerifyUserPermissionsMiddleware middleware instead of the VerifyUserMiddleware in your Django settings:

MIDDLEWARE = [
    # ...
    # 'wagtail_2fa.middleware.VerifyUserMiddleware',
    'wagtail_2fa.middleware.VerifyUserPermissionsMiddleware',
    # ...
]

When this middleware is used, a checkbox is added to the group permissions and 2FA can be enabled or disabled per group.

2FA is always enabled for superusers, regardless of the middleware used.

Sandbox

First create a new virtualenv with Python 3.8 and activate it. Then run the following commands:

make sandbox

You can then visit http://localhost:8000/admin/ and login with the following credentials:

  • E-mail: superuser@example.com

  • Password: testing

Metadata

Release files for wagtail-2fa-new 1.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for wagtail-2fa-new 1.8.0
File Size Uploaded Provenance Actions
wagtail_2fa_new-1.8.0.tar.gz 19.6 kB Without provenance Details for wagtail_2fa_new-1.8.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for wagtail-2fa-new 1.8.0
File Interpreter ABI Platform Actions
wagtail_2fa_new-1.8.0-py3-none-any.whl Python 3 none any Details for wagtail_2fa_new-1.8.0-py3-none-any.whl

Total release size: 44.0 kB

Release files / wagtail_2fa_new-1.8.0.tar.gz

Download URL wagtail_2fa_new-1.8.0.tar.gz
Size 19.6 kB
Tags Source
SHA-256 checksum
How to use checksums
887ab719f17389ea17ad5ad4212e8b4a42a18c6f9eafcda358c20a8362e127d2
BLAKE2b-256 checksum
How to use checksums
591c6bb0606ab1440ed5d7ce48a4af5c99a82255eae057e2d5aa5a8874b0cb66
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.11.9

Release files / wagtail_2fa_new-1.8.0-py3-none-any.whl

Download URL wagtail_2fa_new-1.8.0-py3-none-any.whl
Size 24.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e7b8f6e035d85783b48699561f4277ae892a6b571d86cae3f19d7c77ec75a1cb
BLAKE2b-256 checksum
How to use checksums
07fc5e28db7c6904e8b236b6c541277c156a47586bbd9e0ba87817b393350ca3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.11.9

Security for wagtail-2fa-new 1.8.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.8.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page