On Tue, Jul 1, 2014 at 1:12 PM, guillaume <guillaume.su...@laposte.net> wrote: > > Hi, > thanks for your reply. Actually I don't want to store the uncrypted > password, just submit it to another app registration system, which will hash > it then. The two hashing systems are too different and complicated for me to > use the django encrypted password in the other application database. >
How Django hashes passwords is fully configurable, see: https://docs.djangoproject.com/en/1.6/topics/auth/passwords/ The setting PASSWORD_HASHERS contains a list of classes that hash passwords. Simply replace this with your custom hash algorithm, or calls to your external API that implements your hash algorithm. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFHbX1JGJxCBq8RzA%2B0NA-A%2BOys2s593d3i7m%2B96oM%3Dgxw7x7Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
