On Tue, May 20, 2008 at 10:11 PM, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > > But is it true SSO?
We have 'true' SSO working with multiple Django applications at my workplace, using CAS and an authentication backend based on django-cas; IIRC we're planning to release an updated version to the world at large. I'll check on this tomorrow. > Just sharing the same user database doesn't necessarily help in that > you still have to log in to each application. We actually don't share database across the applications, so logging into each instance (which might just consist of a bunch of redirects if the user's already authenticated to the CAS server) creates a new user object in the Django instance's local database. This even works for multiple instances on the same domain (or not), as long as you remember to use a different SESSION_COOKIE_NAME for each instance. Conceptually, the SSO is done one layer deeper than Django. Individual Django instances are themselves clients to the SSO service (CAS, in this case). Of course, I don't think this has anything to do with what the OP was needing, but your post reminded me of this anyway. Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
