Right now you must be logged-in to cryptid user change-password, which then asks for your existing password plus your new password and a confirmation of the same. But right now the server request takes your auth token and assumes you're authenticated and ignores the current password (actually it may not even be sent.)
We need to update the server to take the existing password plus the new password and confirmation in order to successfully update the password. Then we just need to update the client here to provide all that in the payload to the endpoint.
Right now you must be logged-in to
cryptid user change-password, which then asks for your existing password plus your new password and a confirmation of the same. But right now the server request takes your auth token and assumes you're authenticated and ignores the current password (actually it may not even be sent.)We need to update the server to take the existing password plus the new password and confirmation in order to successfully update the password. Then we just need to update the client here to provide all that in the payload to the endpoint.