#2656: After creating a new user with create_user, calling login is failed
-------------------------------+--------------------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  adrian 
     Type:  defect             |       Status:  closed 
 Priority:  normal             |    Milestone:         
Component:  Core framework     |      Version:         
 Severity:  normal             |   Resolution:  invalid
 Keywords:                     |  
-------------------------------+--------------------------------------------
Comment (by ubernostrum):

 And just to clarify in an utterly pedantic way, based on double-checking
 the code:
 
  * `login` takes two arguments: the `HttpRequest` and a `User` object, and
 updates the session corresponding to the request with info about the user.
 That's it.
  * `authenticate` takes a set of credentials (using the default built-in
 auth backend, this is a username/password pair) and sees if they
 correspond to a valid `User` object, then returns that `User` object.
 
 In other words, any `su`-style functionality has to be built around
 `authenticate`, and that's not a bug -- `authenticate` is, well, how you
 ''authenticate'' people. If you want to do a password-less-style switch
 the way `su` works on Unix when you're root, you can supply a custom auth
 backend which supports that.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2656>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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-updates
-~----------~----~----~----~------~----~------~--~---

Reply via email to