What steps will reproduce the problem?
1. When using Social Sign-in, if user exists, and doesn't match with result
(i.e. from different origin site), it will throw "Incorrect password" error.
What is the expected output? What do you see instead?
The result token stuff should override existing user password (call UpdateUser
if doesn't match).
However, Jaws_User::UpdateUser to change password may mess with XML-RPC. Maybe
we don't XML-RPC password changes when calling UpdateUser...
Original issue reported on code.google.com by alan.val...@ucclouds.com on 13 Feb 2011 at 10:30
Original issue reported on code.google.com by
alan.val...@ucclouds.com
on 13 Feb 2011 at 10:30