I'm at a very similar point in development. To me the only way seems to be to alter the user database and roll my own login methods. This would probably work, but just does not feel right. I'm pretty new to Django, is there something I'm missing? Or is rolling your own really the only way to implement this?
Regards Jonas On Wed, May 7, 2008 at 12:06 PM, Brian <[EMAIL PROTECTED]> wrote: > > I'm building an application where each customer has an account in the > system. That account has multiple users in it, each with their own > username and password. Every account is a separate entity which will > have no knowledge of other accounts or their data. > > Since each customer has their own subdomain, the sites framework seems > like it would work nicely as an account model. I'd also like to use > the built in user authentication system instead of rolling my own. > However, I'm running into a problem: let's say that AccountA > (a.example.com) has a user named UserA. How can AccountB > (b.example.com) also have a distinct user named UserA? Will I need to > set up a whole new database and settings.py for each site? > > Thanks in advance, > > Brian > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
