Re: SAAS User and Auth situation.

@Wes The only problem with using email addresses is that a person could have a User on multiple different accounts and this would not allow for that, unless there was some sort of one-login-to-rule-them- all situation, which there won't be. Imagine a hosted CMS called "Super CMS". A single web

Re: SAAS User and Auth situation.

@Daniel Thanks for muaccounts. I don't know if it'll work because it appears to be coupled to sub domains ( which I may or may not use ). I'll have to dig more into it later tonight. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to

Re: SAAS User and Auth situation.

On Feb 21, 11:09 pm, orokusaki 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

Re: SAAS User and Auth situation.

On 22 February 2010 05:09, orokusaki 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

SAAS User and Auth situation.

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