What is our primary use case?
One Identity Password Manager has been used in our organization for approximately one to 1.5 years in an expertise environment. My primary focus has been on self-service password resets, account unlocks, and enforcing password policies.
The main use case for One Identity Password Manager is enabling self-service password reset and account unlocks for users. It helps reduce dependency on the IT help desk and improves overall efficiency. For example, in day-to-day work, when users forget their password or get locked out of their accounts, they can securely reset or unlock their accounts using predefined authentication methods such as security questions or OTP. This eliminates the need for manual intervention and significantly reduces ticket volume.
Beyond the core use case, One Identity Password Manager plays an important role in improving security and compliance by enforcing strong password policies and enabling secure self-service. It reduces the risk associated with weak or compromised credentials. It also improves user experience since employees do not have to wait for IT support, which ultimately increases productivity across the organization.
What is most valuable?
One Identity Password Manager offers several strong features, but the ones that stand out the most are self-service password reset, account unlock, password policy enforcement, and multi-factor authentication integration. Self-service password reset is definitely the most valuable feature. It allows users to reset their password without IT intervention, which significantly reduces help desk workload and improves efficiency.
Account unlock is another key feature. Users who get locked out due to multiple failed login attempts can securely unlock their accounts through the self-service portal, avoiding delays. Password policy enforcement helps enforce strong password policies across the organization. This ensures compliance with security standards without increasing the burden on the IT team.
What stands out is the integration with multiple authentication methods such as security questions, OTP, and two-factor authentication. This adds an extra layer of security during password reset.
What needs improvement?
While One Identity Password Manager is a strong solution, there are definitely a few areas where it could be improved. One area is the user interface. It is functional but not very modern or intuitive compared to newer password management tools. Improving the UI would enhance user adoption and the overall experience.
The second area is performance and stability. In some cases, performance can be slow, and there have been instances where updates occasionally cause stability issues. A more reliable upgrade process would definitely improve confidence in the product.
The third area is integration complexity. Although it integrates well with systems such as Active Directory, integrating with other platforms can sometimes be complex. Having more out-of-the-box connectors or simpler integration options would be beneficial.
Overall, One Identity Password Manager is a reliable enterprise solution, but improving usability, performance, and integration flexibility would make it even more competitive in today's market.
For how long have I used the solution?
One Identity Password Manager has been used in our organization for two years.
What do I think about the stability of the solution?
One Identity Password Manager has been stable in our experience, especially for core functionalities such as self-service password reset and account unlock. In day-to-day operations, it performs reliably, and we have not faced major disruptions. Users are generally able to reset passwords and unlock accounts without issues, which shows good stability in production.
What do I think about the scalability of the solution?
One Identity Password Manager is quite scalable and handles growth very well, especially in an enterprise environment. Since it is tightly integrated with Active Directory and supports centralized policy management, it can easily handle an increasing number of users without major performance issues. As the organization grows, you can simply extend it by adding more users, domains, or systems without needing a complete redesign.
How are customer service and support?
The customer support experience with One Identity Password Manager has been good. Whenever we have raised a support ticket, especially for configuration or integration-related issues, the support team has been responsive and helpful in providing solutions or workarounds. In most cases, issues were handled through proper guidance, documentation references, or remote troubleshooting sessions. From a technical support perspective, the team is quite knowledgeable about the product.
Which solution did I use previously and why did I switch?
We were previously relying on native Active Directory tools along with manual help desk support for password resets and account unlocks. The main reason for switching was the lack of self-service capabilities. Users had to depend entirely on IT support, which increased ticket volume and caused delays. It was also difficult to enforce consistent password policies, and there was limited visibility and reporting. As the organization grew, this approach was not scalable.
We moved to One Identity Password Manager because it provides a centralized, automated solution with self-service features, better security, and seamless integration with Active Directory. The switch was mainly driven by the need for automation, scalability, and improved user experience.
How was the initial setup?
One Identity Password Manager is deployed in our organization in a hybrid environment. The core system is hosted on-premises, mainly integrated with Active Directory for security and control, while some services such as access capabilities are extended to the cloud to support remote users. The hybrid approach helps us maintain strict control over sensitive identity data while still providing flexibility and accessibility for users working remotely. The hybrid deployment gives us the best balance between security, scalability, and user convenience.
What about the implementation team?
Apart from the core features, one important aspect is the seamless integration with existing systems, especially Active Directory and other enterprise platforms. In our setup, One Identity Password Manager integrates directly with Active Directory, which allows centralized password management and policy enforcement. Whenever a user resets their password, it automatically syncs across connected systems, ensuring consistency and reducing multiple password issues.
It also supports integration beyond just Active Directory. For example, it can extend password management to non-Microsoft systems such as Linux, Unix, and even cloud platforms.
What was our ROI?
The biggest gain was time-saving. Earlier, each password reset or account unlock request used to take around 10 to 15 minutes of IT support time. Now, users can resolve it themselves within two to three minutes. We saw around a 60 to 70% reduction in password-related support tickets, which significantly reduces the workload on the IT help desk team.
In terms of cost, this reduction allows us to avoid hiring additional support staff, especially as the organization scales. For example, we used to receive a high volume of password reset requests every Monday. After implementing self-service, those tickets almost disappeared, freeing up several hours of support time each week. The ROI is clearly visible in terms of reduced support costs, improved efficiency, and better user productivity.
What's my experience with pricing, setup cost, and licensing?
Our experience with pricing and licensing was overall positive, especially considering the value it delivers in an enterprise environment. The pricing is on the higher side compared to some basic solutions, but it is justified given the advanced features, security, and scalability it offers.
Initial setup cost was moderate, mainly because our infrastructure setup and integration with existing systems such as Active Directory require some planning and effort, but it was not overly complex. The licensing is typically user-based, which makes it scalable depending on organizational needs. It is flexible, but for larger organizations, cost planning is important.
Which other solutions did I evaluate?
Before finalizing One Identity Password Manager, we did evaluate a few other options to ensure we chose the right solution. We looked at solutions such as ManageEngine ADSelfService Plus, Okta, and the Microsoft native identity tools with Azure Active Directory. While these tools are good, some lacked the level of customization and deep integration we needed, especially with our existing Active Directory environment. One Identity Password Manager stood out because of its strong self-service capabilities, flexible policy enforcement, and seamless integration with our on-premises and hybrid environment.
What other advice do I have?
Apart from the areas already discussed, I believe support and documentation are two areas where improvements could make a big difference. While the support is generally helpful, response times can sometimes be slower for complex issues. Improving turnaround time and providing more proactive support would enhance the overall experience.
The documentation is detailed, but it can be quite technical and not always easy for new users or admins to follow. More simplified guides, use-case-based examples, and step-by-step tutorials would make onboarding smoother. Additionally, more structured training resources or onboarding modules would help teams adopt the product faster and utilize its full capabilities.
It would also be beneficial to have more advanced reporting and analytics features to better track user activity and security trends. Enhancing support responsiveness, simplifying documentation, and improving onboarding resources would further strengthen an already solid product.
For organizations considering One Identity Password Manager, I recommend starting with a clear use-case focus and strong planning around identity and Active Directory integration. First, define the key problem you want to solve, typically password resets and account unlocks. This ensures quick adoption and measurable ROI early on. Since the tool is heavily dependent on Active Directory, proper domain structure, service accounts, and network connection should be planned in advance to avoid issues later.
I would rate this product 9.5 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure