Re: pre_save on password

2014-07-01 Thread Avraham Serour
you should only store the user password once, if you are trying to catch it just to register in another application then you now have two problems you should set django use the other system as authentication backend, new users should just register there and change their passwords there, on the cen

Re: pre_save on password

2014-07-01 Thread Tom Evans
On Tue, Jul 1, 2014 at 1:27 PM, guillaume wrote: > Hi Tom, > > Yes indeed, I know that page, but there is no way I can make it the same > than the other one which relies on SHA256, some system key I don't know and > a random salt. So there is no way for me to find the correct encryption for > the

Re: pre_save on password

2014-07-01 Thread guillaume
Hi Phil, Actually not at the hasher level, because I need to know the user's details as well, but it's a good hint. I should try to subclass to User Model set_password method. Thanks ! Guillaume Le mardi 1 juillet 2014 15:03:58 UTC+2, Philip a écrit : > > If the username/whatever is availab

Re: pre_save on password

2014-07-01 Thread Philip Mountifield
If the username/whatever is available within the hasher you could create a subclass of the hasher you're using in Django and intercept the plain-text password there, call your API and then call the superclass? Phil On 01/07/2014 13:27, guillaume wrote: Hi Tom, Yes indeed, I know that page, b

Re: pre_save on password

2014-07-01 Thread guillaume
Hi Tom, Yes indeed, I know that page, but there is no way I can make it the same than the other one which relies on SHA256, some system key I don't know and a random salt. So there is no way for me to find the correct encryption for the remote database, that's why I want to use it's API registr

Re: pre_save on password

2014-07-01 Thread Tom Evans
On Tue, Jul 1, 2014 at 1:12 PM, guillaume 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 dja

Re: pre_save on password

2014-07-01 Thread guillaume
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.

Re: pre_save on password

2014-07-01 Thread Rafael E. Ferrero
Sorry... i meant Best Regards (without ? hahahaha... sorry) -- Rafael E. Ferrero 2014-07-01 8:04 GMT-03:00 Rafael E. Ferrero : > I see this too dangerous... it is not a good idea save uncrypted > password... too many hacker attack result on public user-password list. > Why not save encrypted pa

Re: pre_save on password

2014-07-01 Thread Rafael E. Ferrero
I see this too dangerous... it is not a good idea save uncrypted password... too many hacker attack result on public user-password list. Why not save encrypted password on the other application too? Best Regards? -- Rafael E. Ferrero 2014-07-01 6:41 GMT-03:00 guillaume : > Hi list, > > When re

pre_save on password

2014-07-01 Thread guillaume
Hi list, When registering a new user, or a password change, I need to register that user, or his new password, in another application through an internal API. I'm trying to catch the password from the different form they can be found in, but without success. Even the signal pre_save is happenin