On Wed, 2007-10-03 at 00:38 +0600, Densetsu no Ero-sennin wrote:
> On 3 October 2007 (Wed), James Bennett wrote:
> > So don't use set_password(), and avoid any built-in views which try to
> > hash things.
>
> That's not all. I won't be able to use check_password(), which also calls
> get_hexdigest(). And I'll have to reimplement ModelBackend because of that,
> and possibly some other things. And I'll have to tweak admin interface to
> make password changing work. I'd really like to see some cleaner and simpler
> solution.
I think you're colliding two separate problems together here: custom
authentication method and trying to use default methods to manage them.
The first problem is using something other than the default
authentication method (since you want to use a different storage
method). That is solve by writing a custom authentication backend. See
authentication.txt and search the wiki for some more information about
that. You can store the plain text password in a field in the user
profile or wherever you like. Then use the set_unusable_password()
method on the User model to avoid any accidental use of the default
system.
The second problem is try to co-opt the standard User model methods to
work with your custom auth scheme. That isn't what the default auth
system is designed to handle -- if you want to customise, it's done via
custom authentication backends and you are going to have to do the
management of that yourself.
However, some of this automatic use can be done via the fact that Python
is designed to allow methods and functions to be replaced. Import the
User model early enough in your code and then do things like
User.check_password = my_custom_check_password
and so on. No Django core changes required.
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
