New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding an existing user to a new DB resets that user's password expiry #3249
Comments
This flows over into the fact that we need to better notify the user of password expiry |
That should only happen if you set a password. I don't think you need to set a password when importing. If you do, that's a bug. |
@einhverfr yep, @ehuelsmann and I discussed this further in #ledgersmb The simple fix is probably to disable (and ignore) the password field if import is selected.
The same process should be used within user management in the main app. I'd suggest the entire process be written as a small unit with a corresponding dojo widget that "pops up" in a floating div. That code can then be used in both app and setup. |
This commit clarifies the conditions as to when a password should be entered. I've verified (on master/1.9) that the password is *not* a required input field and that not providing a password does not reset the expiry by itself.
This commit clarifies the conditions as to when a password should be entered. I've verified (on master/1.9) that the password is *not* a required input field and that not providing a password does not reset the expiry by itself.
This commit clarifies the conditions as to when a password should be entered. I've verified (on master/1.9) that the password is *not* a required input field and that not providing a password does not reset the expiry by itself.
Resolve #3249: Importing user resets password expiry
Resolve #3249: Importing user resets password expiry
Resolve #3249: Importing user resets password expiry
Resolve #3249: Importing user resets password expiry
So I created a test db yesterday
Then today when I went to raise an invoice I couldn't log in!
The cause, obviously, was the password expiry was reset by importing the user to the new db
At a minimum we should have a loud warning that this is the case.
It would be better to not touch the password nor expiry when importing a user
The text was updated successfully, but these errors were encountered: