Hello, we are using Backendless with Bubble and are getting a strange error on initial sign up and then login. Our user flow is: create a user for someone else, invite them, and they come to Bubble and complete their account. The error displayed says: “Something wrong with old password.” but you can still log in by clicking cancel. The developer has created an individual action for both Backendless and bubble that updates the user’s password, they have also tried to create a temp password during the new creation user process and get the same error regarding an old password in that process as well. Some users can login, and some users can’t. Help please.
Hello,
I have a few clarifying questions for you:
- When a user is invited, do you let them know what their password is?
- The error you mentioned “Something wrong with old password”, does it come from Backendless? or perhaps from your logic in Bubble? I do not recall us having that error message anywhere, I am curious what the actual response is from Backendless. Could you please check?
Regards,
Mark
Thanks for asking these clarifying questions:
Here is our workflow to create a new user:
- We create an account for someone else.
- Assign a temporary password.
- We create a Backendless user (POST Call).
- Update Backendless user’s passwords (PUT Call).
- Send user onboarding email containing Backendless ObjectID and temporary password via URL parameter.
Here’s the workflow for the user updating their account in Bubble:
- Backendless update user call (PUT Call).
– Error displays here: “The Password is not valid” (see attached screenshot). - Again, update the user’s password with the password they choose.
- Update the user’s credentials (Bubble)
- Log the user in (Bubble).
We have always had this error, so as a result, the devs decided to isolate the updating password calls, but it hasn’t resolved the issue.
Note, the error we were getting originally said: “Something Wrong With Old Password” but now it reads: “The Password Is Not Valid”.
Thanks for your help!
Could you please narrow it down to a specific API call into Backendless that returns the error? We would need to see what that call looks like, specifically:
- request body (JSON)
- request headers
- response body (JSON)
Regards,
Mark