1
0
Fork
You've already forked django-allauth
0
Integrated set of Django applications addressing authentication, registration, account management as well as 3rd party (social) account authentication.
  • Python 94.9%
  • HTML 4.2%
  • JavaScript 0.8%
2025年11月27日 10:29:57 +01:00
.gitea chore: issue templates 2025年08月29日 14:35:29 +02:00
.github chore(deps): bump actions/checkout from 5 to 6 2025年11月25日 19:47:58 +01:00
allauth fix(steam): error handling during OpenID discovery 2025年11月27日 10:29:57 +01:00
docs feat(idp): JWT access token support 2025年11月25日 22:23:42 +01:00
examples chore: release 65.13.1 2025年11月20日 17:33:11 +01:00
tests fix(steam): error handling during OpenID discovery 2025年11月27日 10:29:57 +01:00
.dir-locals.el chore: Change formatter in .dir-locals.el 2025年01月24日 15:15:57 +01:00
.djlintrc refactor(templates): Use {% element %} for socialaccount 2023年10月06日 16:33:19 +02:00
.editorconfig feat(account): Separate template for changing email 2023年07月24日 21:32:59 +02:00
.envrc chore: switch to devenv 2025年05月20日 19:49:37 +02:00
.gitignore chore: switch to devenv 2025年05月20日 19:49:37 +02:00
.readthedocs.yaml fix(docs): autodoc not rendering 2023年10月08日 08:55:41 +02:00
.woodpecker.yaml feat: support Django 6.0 2025年11月20日 16:53:10 +01:00
AUTHORS feat(idp): support for wildcards in redirects URIs/CORS origins 2025年09月11日 14:52:01 +02:00
ChangeLog.rst feat(idp): JWT access token support 2025年11月25日 22:23:42 +01:00
CONTRIBUTING.rst tests: move all tests into tests/ 2025年06月21日 14:02:39 +02:00
devenv.lock chore: switch to devenv 2025年05月20日 19:49:37 +02:00
devenv.nix chore(i18n): sync weblate 2025年06月29日 14:24:48 +02:00
devenv.yaml chore: switch to devenv 2025年05月20日 19:49:37 +02:00
LICENSE chore: Preparing release 0.45.0 2021年07月11日 14:39:33 +02:00
Makefile chore: add mise.toml 2025年10月13日 19:27:11 +02:00
manage.py tests: move all tests into tests/ 2025年06月21日 14:02:39 +02:00
mise.toml chore: switch mise.toml to py313 2025年10月17日 14:30:01 +02:00
noxfile.py feat: support Django 6.0 2025年11月20日 16:53:10 +01:00
package-lock.json refactor(ci): nox 2025年05月01日 20:04:11 +02:00
package.json refactor(ci): nox 2025年05月01日 20:04:11 +02:00
pyproject.toml feat: support Django 6.0 2025年11月20日 16:53:10 +01:00
pytest.ini tests: move all tests into tests/ 2025年06月21日 14:02:39 +02:00
README.rst chore: Move project URLs to Codeberg 2024年09月08日 11:57:31 +02:00
requirements-dev.txt feat(headless): JWT strategy 2025年10月17日 13:07:27 +02:00
setup.cfg tests: move all tests into tests/ 2025年06月21日 14:02:39 +02:00

Welcome to django-allauth!

django-allauth logo

ci pypi Coverage Status btc liberapay pystyle jsstyle editor i18n PyPI - Downloads View Django Demo View React SPA Demo

Integrated set of Django applications addressing authentication, registration, account management as well as 3rd party (social) account authentication.

Home page

https://allauth.org/

Source code

https://codeberg.org/allauth/django-allauth

Issue Tracker

https://codeberg.org/allauth/django-allauth/issues

Documentation

https://docs.allauth.org/en/latest/

Stack Overflow

https://stackoverflow.com/questions/tagged/django-allauth

Demo

https://django.demo.allauth.org and https://react.demo.allauth.org

Translations

https://hosted.weblate.org/projects/allauth/django-allauth/

Rationale

Most existing Django apps that address the problem of social authentication unfortunately focus only on one dimension - the social. Most developers end up integrating another app in order to support authentication flows that are locally generated.

This approach creates a development gap between local and social authentication flows. It has remained an issue in spite of numerous common scenarios that both require. For example, an email address passed along by an OpenID provider may not be verified. Therefore, prior to hooking up an OpenID account to a local account the email address must be verified. This essentially is one of many use cases that mandate email verification to be present in both worlds.

Integrating both is a humongous and tedious process. It is not as simple as adding one social authentication app, and one local account registration app to your INSTALLED_APPS list.

This inadequacy is the reason for this project's existence -- to offer a fully integrated authentication app that allows for both local and social authentication, with flows that just work, beautifully!

Features

🔑 Comprehensive account functionality

Supports multiple authentication schemes (e.g. login by user name, or by email), as well as multiple strategies for account verification (ranging from none to mandatory email verification).

👥 Social Login

Login using external identity providers, supporting any Open ID Connect compatible provider, many OAuth 1.0/2.0 providers, as well as custom protocols such as, for example, Telegram authentication.

💼 Enterprise ready

Supports SAML 2.0, which is often used in a B2B context.

🕵️ Battle-tested

The package has been out in the open since 2010. It is in use by many commercial companies whose business depends on it and has hence been subjected to various penetration testing attempts.

Rate limiting

When you expose an authentication-enabled web service to the internet, it is important to be prepared for potential brute force attempts. Therefore, rate limiting is enabled out of the box.

🔒 Private

Many sites leak information. For example, on many sites you can check whether someone you know has an account by input their email address into the password forgotten form, or trying to signup with it. We offer account enumeration prevention, making it impossible to tell whether or not somebody already has an account.

🧩 Customizable

As a developer, you have the flexibility to customize the core functionality according to your specific requirements. By employing the adapter pattern, you can effortlessly introduce interventions at the desired points to deviate from the standard behavior. This level of customization empowers you to tailor the software to meet your unique needs and preferences.

⚙️ Configuration

The required consumer keys and secrets for interacting with Facebook, X (Twitter) and the likes can be configured using regular settings, or, can be configured in the database via the Django admin. Here, optional support for the Django sites framework is available, which is helpful for larger multi-domain projects, but also allows for easy switching between a development (localhost) and production setup without messing with your settings and database.

Commercial Support

Commercial support is available. If you find certain functionality missing, or require assistance on your project(s), please contact us: info@intenct.nl.