I think there's a chapter in the django book about authentication backends, and that's right what you need.
El mar, 04-09-2007 a las 02:28 -0700, Dushyant Sharma escribi�: > hi it might sound strange but what i am thinking is to use two servers > one for authentication only and one for serving normal content. > authentication server can not come into direct contact with users. > here how it goes. > > suppose we have user server USrv and authentication server ASrv. > auth_user table is at ASrv only. > request for log in from the user goes to USrv. Usrv sends it to ASrv > for authentication. If ASrv says the user is authentic then USrv treat > the user as logged in without actually calling authenticate() function > for it. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
