Frequently-asked questions

The following are miscellaneous common questions and answers related to installing/using django-registration, culled from bug reports, emails and other sources.

General

How can I support social-media and other auth schemes, like Facebook or GitHub?

By using django-allauth. No single application can or should provide a universal API for every authentication system ever developed; django-registration sticks to making it easy to implement typical signup workflows using Django’s default model-based authentication system, while apps like django-allauth handle integration with third-party authentication services far more effectively.

What license is django-registration under?

django-registration is offered under a three-clause BSD-style license; this is an OSI-approved open-source license, and allows you a large degree of freedom in modifying and redistributing the code. For the full terms, see the file LICENSE which came with your copy of django-registration; if you did not receive a copy of this file, you can view it online at <https://github.com/ubernostrum/django-registration/blob/master/LICENSE>.

What versions of Django and Python are supported?

django-registration 5.2.1 supports Django 4.2, 5.1, and 5.2, and Python 3.9 through 3.13. See Django’s Python support matrix for details of which Python versions are compatible with each version of Django.

I found a bug or want to make an improvement!

Important

Reporting security issues

If you believe you have found a security issue in django-registration, please do not use the public GitHub issue tracker to report it. Instead, you can contact the author privately to report the issue.

The canonical development repository for django-registration is online at <https://github.com/ubernostrum/django-registration>. Issues and pull requests can both be filed there.

If you’d like to contribute to django-registration, that’s great! Just please remember that pull requests should include tests and documentation for any changes made, and that following PEP 8 is mandatory. Pull requests without documentation won’t be merged, and PEP 8 style violations or test coverage below 100% are both configured to break the build.

How secure is django-registration?

Over the course of django-registration’s history so far, there has been one security issue reported which required a new release to remedy. This doesn’t mean, though, that django-registration is perfectly secure: much will depend on ensuring best practices in deployment and server configuration, and there could always be security issues that just haven’t been recognized yet.

django-registration does, however, try to avoid common security issues:

  • django-registration 5.2.1 only supports versions of Django which were receiving upstream security support at the time of release.

  • django-registration does not attempt to generate or store passwords, and does not transmit credentials which could be used to log in (the only “credential” ever sent out by django-registration is an activation key used in the two-step activation workflow, and that key can only be used to make an account active; it cannot be used to log in).

  • django-registration works with Django’s own security features (including cryptographic features) where possible, rather than reinventing its own.

For more details, see the security guide.

How do I run the tests?

django-registration’s tests are run using nox, but typical installation of django-registration (via pip install ``django-registration``) will not install the tests.

To run the tests, download the source (.tar.gz) distribution of django-registration 5.2.1 from its page on the Python Package Index <https://pypi.org/project/``django-registration`/>`_, unpack it (tar zxvf ``django-registration-5.2.1.tar.gz`` on most Unix-like operating systems), and in the unpacked directory run the following at a command prompt:

python -m pip install nox
python -m nox

py -m pip install nox
py -m nox

Note that to run the full test matrix you will need to have each supported version of Python available. To run only specific test tasks, you can invoke nox with the -s flag to select a single test task, -t to run all tasks matching a particular tag (like docs), or --python passing a Python version to run only tasks for that version. For example, to run tests for Python 3.10 only, you could run:

python -m nox --python "3.10"

py -m nox --python "3.10"

By default, nox will only run the tasks whose associated Python versions are available on your system. For example, if you have only Python 3.11 and 3.12 installed, test runs for Python 3.9, 3.10, and 3.13 would be skipped.

Installation and setup

How do I install django-registration?

Full instructions are available in the installation guide. For configuration, see the quick start guide.

Does django-registration come with any sample templates I can use right away?

No, for two reasons:

  1. Providing default templates with an application is ranges from hard to impossible, because different sites can have such wildly different design and template structure. Any attempt to provide templates which would work with all the possibilities would probably end up working with none of them.

  2. A number of things in django-registration depend on the specific registration workflow you use, including the variables which end up in template contexts. Since django-registration has no way of knowing in advance what workflow you’re going to be using, it also has no way of knowing what your templates will need to look like.

So you will need to write your own templates; for details, see the template documentation, which explains what templates are required and what is available in their contexts.

Configuration

Do I need to rewrite the views to change the way they behave?

Not always. Any behavior controlled by an attribute on a class-based view can be changed by passing a different value for that attribute in the URLconf. See Django’s class-based view documentation for examples of this.

For more complex or fine-grained control, you will likely want to subclass RegistrationView or ActivationView, or both, add your custom logic to your subclasses, and then create a URLconf which makes use of your subclasses.

I don’t want to write my own URLconf because I don’t want to write patterns for all the auth views!

You’re in luck, then; Django provides a URLconf for this, at django.contrib.auth.urls.

I don’t like the names you’ve given to the URL patterns!

In that case, you should feel free to set up your own URLconf which uses the names you want.

I’m using a custom user model; how do I make that work?

See the custom user documentation.

Tips and tricks

How do I close user signups?

If you haven’t modified the behavior of the registration_allowed() method in RegistrationView, you can use the setting REGISTRATION_OPEN to control this; when the setting is True, or isn’t supplied, user registration will be permitted. When the setting is False, user registration will not be permitted.

How do I log a user in immediately after registration or activation?

Take a look at the implementation of the one-step workflow, which logs a user in immediately after registration.

How do I manually activate a user?

In the two-step activation workflow, toggle the is_active field of the user in the admin.

How do I delete expired unactivated accounts?

Perform a query for those accounts, and call the delete() method of the resulting QuerySet. Since django-registration doesn’t know in advance what your definition of “expired” will be, it leaves this step to you.

How do I tell why an account’s activation failed?

If you’re using the two-step activation workflow, the template context will contain a variable activation_error containing the information passed when the ActivationError was raised. This will indicate what caused the failure.