On Fri, 2007-10-26 at 13:31 +0000, Zenom wrote: > Let's say we had a bunch of legacy schemas in postgresql. Currently we > have like 6 schemas if we were to re-write our admin interface from > php to django we would need to write 6 projects 1 for each schema > essentially (if I apply the postgresql schema patches etc, but that's > beside the point). > > My question would be this: Is it possible to maintain a login state > across all 6 projects, if they were situated at mysite.com/admin1 > mysite.com/admin2 etc etc. This way we could code each piece into > it's own admin?
Natively, Django can't do what you want, since the login state is part of the session, which is referenced via a cookie, so you have cross-domain restrictions. You might be able to get somewhere with a custom authentication backend (see the authentication docs) and passing a token around as part of the URL, but it would take some investigation. Essentially, you're asking for single sign-on, which is a difficult problem in general because of the cross-domain requirements. But that's the area to look in. Regards, Malcolm -- I don't have a solution, but I admire your problem. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
