On Tue, 2005-08-02 at 18:28 +0000, Django wrote: > I made it work with the users going in django.models.auth. But it is > not a very good solution as it becomes project-wide and I cannot have > another similar application. > > I think we need to have a way to tell the auth/sessions framework the > correct user tables to use. It is hardcoded to pick the > django.models.auth table only!
Just to chime in on this: I would like to be able to have users authenticated against something else entirely (an LDAP server), while still supporting sessions in some convenient manner. Ideally I would also have credentials stored on the browser side (Basic-Auth over SSL or Digest-Auth) rather than stored in session files on the server, but that's a separate issue, I suppose. Can anyone suggest how I ought to go about plugging an alternative authentication model into Django? Or should this kind of thing be on the devel list? -- +----------------------------------------------------------------+ | Jason F. McBrayer [EMAIL PROTECTED] | | "If you wish to make Pythocles wealthy, don't give him more | | money; rather, reduce his desires." -- Epicurus |
