On Feb 21, 11:09 pm, orokusaki <flashdesign...@gmail.com> wrote: > I'm developing an SAAS which means that I will have Accounts and those > Accounts will have Users. Each account's Users are completely > orthogonal to the Users of another Account. When a user logs in, > they'll supply an Account ID, a username, and a password so username > only needs to be unique with regards to the Account in question. > Firstly, is there an app out there or somebody who knows how to > conquer this? If so, I would truly appreciate the help or a link. > Problem 1 (with built-in User object), maybe there is a way around > this: > > A) User of Account 'acme' might have the username "mike" and the user > for Account "general mills" might have a user with the username > "mike" (since "mike" is a very common name this will certainly happen > within the first day of getting clients). I can't control what > Accounts' Users decide to make their username and I certainly don't > want to make it like domain registration, like if a User has to check > if a username is available before creating it (all common names would > be taken after the first 100 accounts if the average account had 2-3 > users).
There are patches for using email addresses (u...@account) as usernames. [1] I'm not sure how to ensure unique account usernames without checking for uniqueness. [2] You may be looking for something like a custom authentication backend. [3] Or OpenID. [1] http://groups.google.com/group/django-developers/browse_thread/thread/9fcc44c5f99beb21/3420dc565df39fb1 [2] http://code.djangoproject.com/wiki/MultipleColumnPrimaryKeys [3] http://docs.djangoproject.com/en/1.1/topics/auth/#other-authentication-sources -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
