Django Multi-Tenant All-Auth

543 views
Skip to first unread message

Erik Dykema

unread,
Nov 18, 2014, 2:10:24 PM11/18/14
to django-...@googlegroups.com
Hello-

I'm new to Django-Allauth but it seems like a very cool project, thanks to the devs and the community for creating and supporting it.

We'd like to put together a "seed" repository on Github which combines the best aspects of django-allauth and also django-tenant-schemas (or some other multi-tenant approach).  The idea being, these days, there are two big capabilities that a lot of devs want to have their application to have: first is registration / social login / etc; and django-allauth does this very well.  Another is, multi-tenant capability.  These two things are both tricky on their own, and also hard to put together, but if we got them together then people would be able to quickly bootstrap one of the more common web design patterns in use these days.

If anyone is interested in collaborating on this, either on a shared-development basis, or as a paid project, please let me know by responding to this thread.  Some more detail on the requirements below.

thanks,
Erik

=Django Multi-Tenant All-Auth Seed Project=

We'd like to build a demo / "Hello World" type project, using Django 1.7, django-all-auth, and django-tenant-schemas, that does the following:

  1. Provide signup / registration / password change/reset/etc. workflows from django-allauth for new users, (e.g. at app.mydomain.com).  This seems like standard allauth stuff.
  2. Each time a new user registers, create a new "tenant," (e.g. standard django-tenant-schemas stuff).
  3. Permit users to login through a central place, (e.g. at app.mydomain.com
  4. On login, redirect logged in users to their proper tenant (e.g. user12.app.mydomain.com)
  5. Users are not authorized to use other tenants (e.g. user12 cannot access user15.app.mydomain.com)
  6. When they're logged in, their requests / views / etc. only show information from their tenant; for example, if "document" was a tenant-only model then they could see only documents for their tenant (e.g. standard django-tenant-schemas stuff).

Perhaps, boiled down to its bare bones and re-stated; we'd like to develop the equivalent of a "seed" project which combines django-tenant-schemas and django-allauth; to create the bones on which one could build a multi-tenant web app.

Roselle Ebarle

unread,
Aug 17, 2018, 4:34:26 AM8/17/18
to django-allauth
Hello, 

Was this boilerplate ever implemented successfully? I'm trying to do the same. 
Reply all
Reply to author
Forward
0 new messages