When it comes to user credentials, it needs to be treated a bit differently. What you probably have to do, is to basically include the full payload of the old usercredentials with the new password. It does not support matching on anything else than “user”: { “id”: “…” } which is required. Please be aware that in 2.21, this field has been renamed userInfo. I know its a bit weird that you have to point to the same user that you are updating, but this is how the model currently is.
···
The code / username issue, in the usercredentials class the getCode property has been overriden to be username, there is no real reason for it (I think), but thats the reason you see this.
–
Morten
On Wed, Oct 7, 2015 at 9:05 PM, Jose Garcia Muñoz josemp10@gmail.com wrote:
Hi Morten, all,
We need to update the passwords of several users using the Web API. We are trying the following API call: