Hi,
Thanks for this great package. It's very complete, functional and flexible enough to work with any kind of shiny projects. And its functions are so clearly and logically scripted that even the scarce documentations helps perfectly.
There's one issue I couldn't resolve yet: when a user is marked with "change password on next connection" flag, the login process falls in a loop. The updated password is clearly stored at the dddd: the next time doesn't allow the password set in previous attempt because of "New password cannot be the same as old". But still in any new attempt of login the UI asks to change the password.
A query on psw_mngt shows that the must_change value for the user just created remains in 1 even after the password update. So, the issue is on the communication between shinymanager and MariaDB. But I didn't get yet where it breaks.
Any idea?
Hi,
Thanks for this great package. It's very complete, functional and flexible enough to work with any kind of shiny projects. And its functions are so clearly and logically scripted that even the scarce documentations helps perfectly.
There's one issue I couldn't resolve yet: when a user is marked with "change password on next connection" flag, the login process falls in a loop. The updated password is clearly stored at the dddd: the next time doesn't allow the password set in previous attempt because of "New password cannot be the same as old". But still in any new attempt of login the UI asks to change the password.
A query on
psw_mngtshows that themust_changevalue for the user just created remains in 1 even after the password update. So, the issue is on the communication between shinymanager and MariaDB. But I didn't get yet where it breaks.Any idea?