Zango AllAuth - Authentication for Zango
A multi-tenant aware fork of django-allauth, purpose-built for the Zango Django framework. This package provides comprehensive authentication and authorization capabilities designed to work seamlessly with Zango’s multi-tenant architecture.
Zango is an enterprise-ready Django framework that enables rapid development of business applications with built-in multi-tenancy, security, and compliance features. Learn more at https://zango.dev
Zango AllAuth extends django-allauth to provide:
Multi-tenant Authentication: Isolated authentication contexts for each tenant
Role-based Access Control: Seamless integration with Zango’s role and permission system
Social & Enterprise Login: Support for OAuth, OIDC, SAML 2.0, and more
Account Management: Comprehensive user registration, verification, and account management
Enterprise Ready: Built with security and compliance in mind
Resources
- Zango
Home: https://zango.dev Documentation: https://zango.dev/docs GitHub: https://github.com/Healthlane-Technologies/Zango Discord: https://discord.com/invite/WHvVjU23e7
- Zango AllAuth
Source code: https://github.com/Healthlane-Technologies/django-allauth/tree/zango_allauth Bug Tracker: https://github.com/Healthlane-Technologies/django-allauth/issues
- Django AllAuth (Original Project)
Home page: https://allauth.org/ Source code: https://codeberg.org/allauth/django-allauth Documentation: https://docs.allauth.org/en/latest/
Why Zango AllAuth?
Zango AllAuth is a specialized fork of django-allauth created to seamlessly integrate with Zango’s multi-tenant architecture and enterprise features.
Key motivations:
Multi-Tenant Support: Zango runs multiple independent applications on a single server. Authentication must be tenant-aware, isolating user data and permissions by application instance.
Role-Based Access Control: Zango provides built-in role and permission management. AllAuth needed adaptation to work within this system while maintaining per-user, per-role authentication contexts.
Enterprise Features: Modern applications often require multiple authentication methods (local accounts, social login, enterprise SSO). Zango AllAuth provides a unified authentication layer supporting all scenarios out of the box.
Simplified Integration: Rather than cobbling together separate authentication packages, Zango AllAuth integrates seamlessly with Zango’s configuration, deployment, and permission systems.
By combining django-allauth’s battle-tested authentication logic with Zango’s multi-tenant and role-based architecture, Zango AllAuth provides enterprise-ready authentication for rapidly developed business applications.
Features
- 🏢 Multi-Tenant Authentication
Authentication contexts are isolated per tenant. Each Zango application maintains its own user database, roles, and permissions with complete data isolation.
- 👥 Multiple Authentication Methods
Supports local authentication (username/email), social login via OAuth 2.0 and OpenID Connect, SAML 2.0 for enterprise SSO, and custom authentication protocols.
- 🔐 Role-Based Access Control
Seamless integration with Zango’s role and permission system. Define fine-grained permissions at the application level with easy-to-use policy definitions.
- 💼 Enterprise Ready
Built from the ground up for enterprise applications. Includes SAML 2.0 support, account enumeration prevention, rate limiting, and comprehensive security features.
- ⚙️ Smart Configuration
Provider credentials can be managed via Django settings or the Zango App Panel admin interface. Configuration per-tenant allows different authentication providers for different applications on the same deployment.
- 🔒 Security First
Built-in rate limiting, account enumeration prevention, email verification, and secure password management. Battle-tested since 2010 with contributions from commercial organizations.
- 🧩 Extensible Architecture
The adapter pattern allows customization of authentication flows. Override adapters to inject custom logic at key points in the authentication process.
- 📱 Progressive Enhancement
Support for modern authentication features including multi-factor authentication, social account linking, and email address verification across all authentication methods.
Metadata
Release files for zango-allauth 65.10.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| zango_allauth-65.10.0.tar.gz | 1.6 MB | Without provenance | Details for zango_allauth-65.10.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zango_allauth-65.10.0-py3-none-any.whl | Python 3 | none | any | Details for zango_allauth-65.10.0-py3-none-any.whl |
Total release size: 2.8 MB
Release files / zango_allauth-65.10.0.tar.gz
| Download URL | zango_allauth-65.10.0.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4523f08d2ebc4bbe390c5fe2de87bbefc3ece55deaff9b029b4bd91acaa64b81
|
|
BLAKE2b-256 checksum How to use checksums |
4590c32cca06b88b720554d82a8577aaf409a1b8410cacdb0f763b3d821cc606
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / zango_allauth-65.10.0-py3-none-any.whl
| Download URL | zango_allauth-65.10.0-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1728ef82d8ea7a3878fd034673b77d00802d7e7f379a3be86e92cd1219b5f510
|
|
BLAKE2b-256 checksum How to use checksums |
ce5b4badf7676961ba844601703026650612aacb221b2fec8429bbd0d54647b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for zango-allauth 65.10.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.