Okay. If you want to have multiple webapps authenticating off a single user
base, then you will need to either:
- Expose a server side authentication system (basically your own mini
network of OpenID)
- Merge all the sites into a single Django webapp.
If you have a look through the mai
On Thursday, June 16, 2011 2:38:52 PM UTC+2, SleepyCal wrote:
>
>
> Having a central authorization point is the way forward. I'm a bit confused
> by this comment though:
>
> "But this still do not solve problem of NOT having multiple accounts in
> several django projects"
>
> Could you explain
On Thu, Jun 16, 2011 at 1:26 PM, DK wrote:
> Hi,
>
> I need to develop several django projects (let's assume that there are
> highly different one from each other). The common thing is users/groups
> data. If a user register into one of this sites, he should be able to use
> this same account cre
How about Celery & RabbitMQ?
Use Django's signaling functionality to kick off a Celery task, use
Celery to make it async and nearly real-time, then transfer the info
securely.
I recommend *not* allowing the data to be serialized in the RabbitMQ
message (for security & performance), but rathe
Hi,
I need to develop several django projects (let's assume that there are
highly different one from each other). The common thing is users/groups
data. If a user register into one of this sites, he should be able to use
this same account credentials for all other sites.
I really didn't find a
5 matches
Mail list logo
