I am in the transition process of moving between Milestone 2020 R2 to Milestone 2023 R2. In our enterprise, we use log in scripts to open our basic user accounts. Using our current Smart Client Version 2020 R2, the login action works as expected. Upgrading to the 20223 R2 version, this action is now noted. Running the script the first time works. After that it no longer works. What I have noticed is that the login history is now recording the username and password. The Password is changed to “password2”. Changing the password in the login history works…until the script runs and then the login history file changes the password back to “password2”. Comparing this action to the 2020 R2 version, the login history file does not record the basic user being logged in. There is no change to the login history file, until someone manually signs into the Milestone Client 2020. The login file I am referring to is in:
[C:\Users\USERX\AppData\Roaming\Milestone\Smart](file:C:/Users/USERX/AppData/Roaming/Milestone/Smart) Client.
One work around attempt was to allow the “Remember Password” feature. Yes, it does work to allow the login. But. The user is able to copy the password and then view the password. That action cannot be allowed. This also allows the basic user to attempt to change the password or at least lock the account by inputting the wrong password too many times.
My thought process is to ask for the solution that does not allow the login history file to record the basic user information. Is that an option or is there another solution?