- Edited
Hello,
I have successfully created a new modification in order to reset and get the new password for Admin/Manager/Staff, hereinafter refferred to as Helpdesk Officer (HO), just in case if they forgot their password without having ask the webmaster or admin to reset/update the password by doing md5 via phpMyAdmin or another MySQL tools to database directly.
The general info about this new feature is that we need an activation key that sent to the HO's email who request it, in order to activate the new password. After HO activate the new password, then osTicket will send the new password to HO's email. So, this will prevent somebody who acts as another person trying to reset the password belongs to somebody else. That's the main idea!
Here is the normal scenario I made:
1) There is a new link named "Forgot Password" beneath the password textbox in login page in SCP.
2) HO forgot their password, then click that link.
3) HO enter their email, then click the "Send My New Password".
4) osTicket send an URL link to the email for activate the new password
5) HO check the email, then find there is a URL link in that email.
6) HO have to click that link in order to activate the new password.
7) Password activated, osTicket send the new password to the email.
8) HO check the email, and now can login as usual using the new password.
Ubnormal scenario:
1) If the email that entered by HO does not exist in the system, osTicket will display the message to inform that the email does not exist.
2) If HO supply the wrong activation key on the URL, then osTicket will display the message to inform that the activation key is wrong and the password never been changed. Also, after the new password being activated, then the activation key will never work anymore.
3) If staff A knows the staff B's email, staff A is still able to enter staff B's email in Forgot Password page, and osTicket will send the activation URL link to staff B's email, but, since the staff B never request this new password, as long as staff B never click on this activation link, then the password will never changed. In other word, staff B is still able to use the old password if he/she ignores that activation link.
Feel free to give any feedback regarding this modification by replying this topic.
Actually, it is almost finished, and so far its progress is about 85%. I will publish the final result after 100% completed.
So, stay tuned everyone! ;)
Sincerely,
Masino Sinaga