Skip to main content

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

Project description

https://github.com/pennersr/django-allauth/actions/workflows/ci.yml/badge.svg https://img.shields.io/pypi/v/django-allauth.svg Coverage Status https://pennersr.github.io/img/bitcoin-badge.svg https://badgen.net/liberapay/receives/pennersr https://img.shields.io/badge/code%20style-pep8-green.svg https://img.shields.io/badge/code_style-standard-brightgreen.svg https://pennersr.github.io/img/emacs-badge.svg https://hosted.weblate.org/widget/django-allauth/django-allauth/svg-badge.svg

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

http://github.com/pennersr/django-allauth

Mailing list

http://groups.google.com/group/django-allauth

Documentation

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

Stack Overflow

http://stackoverflow.com/questions/tagged/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, 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.

Cross-Selling

If you like this, you may also like:

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-allauth-async-fix-0.61.0.dev0.tar.gz (799.4 kB view details)

Uploaded Source

Built Distribution

File details

Details for the file django-allauth-async-fix-0.61.0.dev0.tar.gz.

File metadata

File hashes

Hashes for django-allauth-async-fix-0.61.0.dev0.tar.gz
Algorithm Hash digest
SHA256 f2ca22194798df502b26036600a060f9a4042c19892fdfc7d7696f9bf673e5d4
MD5 517f180b9e4e338cf365f5951c1627b5
BLAKE2b-256 9944c42632d86aeef29e1aa52623d994207fcb11b5f1b8b878d7ae7089cd9340

See more details on using hashes here.

File details

Details for the file django_allauth_async_fix-0.61.0.dev0-py3-none-any.whl.

File metadata

File hashes

Hashes for django_allauth_async_fix-0.61.0.dev0-py3-none-any.whl
Algorithm Hash digest
SHA256 09cf5a671ba44eff638ba8628c88be2862b69eb74fa4c6b6f9e2944569d69e0c
MD5 1b817a2c179b4fa07d9a37ba655faa3a
BLAKE2b-256 4a01d393619c0a9ba8561a42a54ceb3d3515e2000791c7149ffadf9ec746613b

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page