06-09-2019, 05:05 PM
Coming back to this issue, I’ve tried to find a solution, but it fails.
Here’s the scenario:
- The App requires users to register an account and log in.
- Now, User has forgotten his password.
- The App provides means for checking User email exists and generates a token, sent to User by email.
- To do this, and save the token to the cloud database, the App must authenticate with a universal account. So it does that per default at startup.
- User provides correct token, and a new password should be saved to the user’s account using cdb_updateUserAccount
- The App tries to update the User's account by calling cdb_updateUserAccount tData,tProjectName,”User’s email”
- LiveCloud instead updates the App’s universal account…
Even though it has a different email. The universal account is indeed the LoggedInUser, but it specifies another account for the update.
So, is it a bug, or am I doing something obviously wrong? How can my app update the data (specifically the password) of a user who is not the LoggedInUser?
Here’s the scenario:
- The App requires users to register an account and log in.
- Now, User has forgotten his password.
- The App provides means for checking User email exists and generates a token, sent to User by email.
- To do this, and save the token to the cloud database, the App must authenticate with a universal account. So it does that per default at startup.
- User provides correct token, and a new password should be saved to the user’s account using cdb_updateUserAccount
- The App tries to update the User's account by calling cdb_updateUserAccount tData,tProjectName,”User’s email”
- LiveCloud instead updates the App’s universal account…
Even though it has a different email. The universal account is indeed the LoggedInUser, but it specifies another account for the update. So, is it a bug, or am I doing something obviously wrong? How can my app update the data (specifically the password) of a user who is not the LoggedInUser?