In my company, we use the solution's dictionary rule to see the availability of passwords or for the integration to other external systems with two-factor authentication.

I work for a company that implements products.

We use One Identity Password Manager to reset passports after a vacation. People forget their passwords while on vacation.

My organization implemented this solution for clients. I was a developer on the reseller team. We used version 5.9.

I have been using One Identity Password Manager for approximately one year.

* Allow end users to reset AD password by either answering security questions or by generating OTP

* Reduce load on helpdesk

* Allow end user self-service outside office hours by allowing access to self-service portal from outside corporate network

The primary use case for One Identity Password Manager is for a user to reset the password himself. For example, if the end-user goes on vacation or emergency leave, after some time when that user returns to work, he could forget his password. That end-user can ask the system administrator or Active Directory administrator to reset the password because there's a way for the administrator to crack the password for the user. Still, if the user has One Identity Password Manager, he can reset the password by answering a few questions correctly. He'll be able to answer the questions if he sets the questions on One Identity Password Manager before the password reset.

Implementing One Identity Password Manager is better because it can provide better security. For example, the administrator could reset the password without knowing whether the person requesting the password reset was the actual user and not a scammer.