Eh, it’s about validating credentials match the records of the user account, it’s not about validating that the person using those credentials is who they say they are. In other words, it doesn’t mean “the person logging in is John Smith,” it means “the person logging in has John Smith’s credentials.” If you want to prove that the user is who they say they are, you’ll need a lot more than a password (biometrics are a start).
I imagine this process is more about ensuring the employee is the one entering the new password, rather than the malicious actor - which would easily be possible if a simple password reset email was sent out.
I guess that’s possible, but then that user would be locked out of their account and they’d quickly figure out whose account was compromised when the employee can’t access things anymore.
Eh, it’s about validating credentials match the records of the user account, it’s not about validating that the person using those credentials is who they say they are. In other words, it doesn’t mean “the person logging in is John Smith,” it means “the person logging in has John Smith’s credentials.” If you want to prove that the user is who they say they are, you’ll need a lot more than a password (biometrics are a start).
I imagine this process is more about ensuring the employee is the one entering the new password, rather than the malicious actor - which would easily be possible if a simple password reset email was sent out.
I guess that’s possible, but then that user would be locked out of their account and they’d quickly figure out whose account was compromised when the employee can’t access things anymore.