On Nov 28, 12:06 pm, Brian <[EMAIL PROTECTED]> wrote: > > For each account, through what do they login initially? Are you > > expecting to use Django based login mechanisms for that, or do you > > front it all with HTTP Basic Authentication. If you are going to > > somehow switch based on their identity it presumably needs to be done > > outside of the context of the target Django instance else you will not > > know which to go to. > > This is a good question, and I haven't come to a conclusion. Probably > it'll be the Django built-in application-based authentication, > particular to each Django instance. There will be a master map of all > users to their respective Django instance.
That seems a bit like a chicken and egg problem. At the point that you need to make the decision as to which Django instance to use, you haven't yet logged in them in. Thus if you are going to try and use their own instance to log them in, that can't work. If you use one special Django instance to handle login, then issue is having any session information in that instance also used by the other instances such that when you go to actual instance on subsequent requests, it knows you are allowed to access it. I'll describe any solution in terms of HTTP Basic authentication first and then can let you think about authentication when you see how the multiplexing is achieved. Graham --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
