Comment 2 for bug 693474

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

This still occurs when connected with XMLRPC.

Possible solution is:
1. Trap the object change.user.password(as we do for res.users,as these are 2 special cases)
2. Pass a context when calling button : <button colspan="1" icon="gtk-ok" name="change_password" string="Change" type="object" context="{'change_password':confirm_password}"/>
3. Interrupt the rpc_exec_auth() and trap the args if the object is change.user.password and change gw_inter._passwd to be the new password.

More Investigation can help getting more suitable solutions.