I had an issue where i can not edit few users in Users Collection.
It being caused by the temporary password.
Found the cause. When saving a User from the database editor, the request
payload sends “temporary_password_expires_at”: “[hidden]” (the masked
placeholder) instead of omitting the field. For users where that field is
null (e.g. user 116, or newly created users) saving works; for users that
have a temporary password expiry set, the server returns
500 Internal Server Error. The editor should not send masked “[hidden]”
fields back on save.
Now, i made a test with one of the users i control and after use the option “Forgot Password” which give no chance to set new password after login with the temporary one, i went to my change password input (which always being working) and now the white canvas is on loading and i can not access to the screen flow.
You might need to wait 24 hours for the temporary password to expire. Could you try going forgot password in the app and creating a new password? (Then refresh the editor and try editing the user record again)
So you created a new password through forgot password in the app and logged in to the app, but still not able to edit the user through the collections editor? Collection permissions?
What kind of properties you’re trying to update for the user or just the password, through the collections editor?
Did you tried after reloading the browser tab or clearing your cache? What do you see in the network tab? If not working, might need a deeper look. Could you share the app url?
I totally found the issue.
I have a Screen Interim which redirects users. That redirection steps away from the screen to set the new password after login with the temporary one and that locks the process.
Yes, this is an issue reported but not fixed yet as far as I’m aware. (will check with the team) Same happens like when sending from login to a IAPHUB start screen, and then to home from the start screen. The current solution would be to build the forgot password process custom.
@JareRamirez, it seems the error is due to a recent change, it should be fixed now! Could you reload the editor and try again editing the users in the collections view?