You have to use ``auth.models.User`` if you want to enjoy all the benefits of the auth system. Just create a model and make a onetoone to User.
On Apr 2, 8:22 am, Heit <[email protected]> wrote: > Hello, > > I'm newbie in django, reading documentation i understood that django > authorization model is based on django.contrib.auth.models.User class > and without having an instance of it, it is impossible to maintain > authentication and maybe an authorization. Even if I'll write my own > authentication backend i have to create an instance of > django.contrib.auth.models. User or it's subclass which corresponds to > the record in database table auth_user. Does django support a way of > authentication where i needn't create a record in auth_user table. May > be there is away like java portlet authentication where i can call > something like request.getRemoteUser() ant receive a string > representing an unique key of user and then to use this key in > authentication checks. -- 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.
