Identity Manager by One Identity Reviews

My main use case for One Identity Manager is for identity access management solutions for clients. For our clients, let's say we have a bank company as a client. In that client, there will be employees, various kinds of employees, permanent employees, external employees, vendors, so many people might be there. Every employee who gets onboarded into a company will be having some identity within the company, so to provide an entire identity access management system is essential.

Once a user is onboarded, we can give some accesses by default using birthright roles or dynamic roles. We can also provide a way so that the user can request the roles or accesses that the user might require. We have a portal, IT Shop, everything set up, and we can create workflows, access approval workflows, and all so that the user can request the required access, and if the proper workflow has been completed, the access will be provided. These all things can be customized as per the customer requirements.

Using One Identity Manager, we can connect with various target systems like ServiceNow, SuccessFactors, Workday, whatever, however. To One Identity Manager, we can onboard data, and we can also send the data to various target systems, whatever the customer might need. It provides various connectors such as DB connector, native SQL connector, Oracle connector, SAP connector, Exchange connector, Active Directory connector, PowerShell connector. There are so many ways we can connect to other systems so that we can send data to other systems and sync back from those systems, making this One Identity Manager system a centralized system that controls everything. One Identity Manager can act as a source of truth for various systems, which is one way for the companies to centralize their IM system.

In my opinion, the best features One Identity Manager offers are customization. We can customize many things as per our requirements, not just use the default options, out-of-the-box options. We can connect to any target system using the PowerShell connector, which is the best way. We also have API connectors and other things as well. From the latest versions, they are moving from the native portal to the Angular portal, which will speed up the portal development process and make the portal more attractive and dynamic. It also has other supportive portals like Operations Portal, Admin Portal, and Password Reset Portal for various services and all.

Most customers choose One Identity Manager because of the customization it provides, not just for me or my customers. We have one feature called attestation, which helps review user access periodically and frequently and ensures the audit players and audit processes work properly within the organization.

One Identity Manager positively impacts my organization and my clients by automating user access reviews, which often won't happen properly. With One Identity Manager, we can schedule those access review processes and automate them so that they automatically trigger and send access review emails to the user's managers, ensuring they take action on the access side, whether the user should have that access or not. For most customers, their access management system becomes smoother using One Identity Manager.

The specific outcomes my clients have seen include saving time and reducing manual work. Without a centralized IM system like One Identity Manager, onboarding tasks must be done manually, leading to human errors. If a user makes a mistake manually, it could lead to another incident, causing bottleneck issues in operations. Using a centralized system like One Identity Manager really eases the onboarding and offboarding processes for any organization, making identity access management smoother.

One Identity Manager could be improved because the community is a bit small, and the documentation sometimes isn't clear or interactive. This migration from the native portal to the Angular portal is not well known, and I think this change could bring chaos within the community.

I have been using One Identity Manager for more than two and a half years.

One Identity Manager is stable in my experience.

One Identity Manager's scalability depends on the subscription you take and the size of your user base.

Customer service rating: 4 out of 10.

I evaluated SailPoint, Saviynt, and other tools before choosing One Identity Manager. I prefer One Identity Manager because of the customizations it allows, though I'm not completely certain about other solutions. My experience with One Identity Manager influenced my choice.

When using a centralized system like One Identity Manager that offers so much customization, I see a return on investment through saved money. Instead of spending on various systems, having one centralized system that handles all my organizational requirements helps save money. The setup is easy, and One Identity Manager provides support.

I advise others looking into using One Identity Manager to go ahead and take the latest version of One Identity Manager solution to avoid the headaches of migrating from previous versions. The latest versions have support from One Identity Manager as well, fixing many issues and adding new features as part of the new releases. Our company has a business relationship with this vendor as we are partners. I rate this solution an 8 out of 10.

We use it for identity management and governance. We are a large financial institution; therefore, we use it for identity management and all the cases surrounding that, such as segregation of duty, attestation, extensive provisioning, and life cycle management.

The largest improvement we have seen is the depth of how many applications we have covered. We have about 4,000 applications connected to One Identity Manager, fully managed from there. That has definitely grown over the years, including the ease of connecting those applications. In the end, what we want to achieve as an organization is not a nice technical solution, but our goals are being in control of our accounts, being in control of our entitlements, and being in control of what entitlements are assigned to whom and why, and proper substantiation for that. To be able to achieve that, we need to have a large range of applications that we actually manage. That is something that has become easier and grown over the years. I would say this is the biggest improvement. Moreover, better processes have been introduced surrounding the data so that we do not just connect the applications, but at a data level, we actually achieve the control we want by ensuring everything in those applications is monitored and kept in control.

The SAP integration goes in-depth into the SAP tool, enabling us to get all the information we want from there. It connects SAP accounts to employee identities under governance, which is very important. It saves licensing costs by cleaning up and ensuring SAP accounts are associated with actual employees. We want a SAP account associated with one person.

It provides IGA for the difficult-to-manage aspects of SAP, such as T Codes, profiles, and rules. It provides profiles, profile limits, and field values.

It offers a single platform for enterprise-level administration and governance of users, data, and privileged accounts. It is very good, especially when you are looking at the enterprise backend. On the platform side, it is very good. However, the frontend usability, at least for our organization, could still be improved a little bit. That is not so much for the admin perspective; that is for the actual end-users in our enterprise. That is partially also due to the fact that we are still using some of the older portals because we have been using the tool for a while, and we have not had a chance to migrate to all the latest versions. It is very good for enterprise management, but our end-user experience could still use some fine-tuning, tweaking, and improvements.

We can easily customize the solution for our needs.

We use the solution's business roles to map company structures for dynamic application purposes. That is very important for us because it is one of the ways where we can remove the complexity for end-users. We can automate things while still providing a good control framework where we can say we are in control. Being a large enterprise, we have a complicated structure, so we need a good model that allows us to accommodate that complicated structure. With the business roles, we were able to do that.

We use it to extend governance to cloud apps. This extension is important for us because, as a large financial institution, we have to meet a lot of compliance requirements. That does not stop with our on-premise environment; it also applies to our cloud systems, so we need to manage those.

It helps minimize gaps in governance coverage among test, dev, and production servers. We also have a lot of our dev, test, and acceptance environments connected to the solution. It allows us to manage those as well based on the production user's life cycle. We have no issues there.

It helps consolidate procurement and licensing a little bit. We do not manage our procurement or licensing in the tool. We have our own procurement tools for that. However, when we know, for example, that there are limits to the amount of licenses we can give out, we use the tool to ensure we do not pass those limits. We use it more as an enforcement tool or safety valve to ensure we follow the guidelines set by procurement on how much we can do.

It streamlines application access decisions, application compliance, and application auditing. We use the segregation of duty framework. We use the attestation framework. It is one of the core pillars for the regulatory and compliance set where we show we are in control of our identities, accounts, and the access they have. We can show that we meet all the regulations in regular reviewing that ensure that no toxic combinations or toxic pairs are assigned.

It helps achieve an identity-centric zero-trust model. We are currently using it for one body, and we are looking into extending it to machine identities. For our current human employees, we are in the identity-centric model. We also have multiple sources from where identities come. We have a lot of subsidiary companies. We have a lot of statements of work or external contractors, and sometimes people come in from multiple sources at the same time. It also allows us to consolidate that to see that it is actually the same identity.

It helps create a privileged governance stance to close the security gap between privileged users and standard users. For the management of privileged accounts, we use another solution called CyberArk Privileged Access Management, and we do have a close automated connection between One Identity and CyberArk where we use One Identity to decide who should have access to which privileged accounts and why. CyberArk is a tool that we use to actually hand out access to those accounts and monitor usage of those accounts, etc. The governance part of who can use which account is managed from One Identity, and then the actual usage is done through CyberArk, and that integration works well for us.

What I like the most is the flexibility or configurability. It is not like you are writing huge lines of code. It allows us to handle our very complex enterprise use cases, and we have many of those. We have a lot of scenarios where we need to do things internationally or slightly differently per country, or need to comply with specific regulations. It gives us a lot of flexibility to meet all those needs while also being able to accommodate our enterprise processes. It allows us to shift the tool to work for us instead of needing to change the organization to follow a piece of technology.

Their support could be enhanced.

There is an area for improvement when it comes to intuitiveness. It has the ability to manage everything and does that fairly well, but that also causes a risk of drowning end-users in complexity. One Identity technology probably has the best way to handle the complexity that you want to tackle as a large enterprise. It can handle any complex use case you can think of, but that is also the thing they should improve on. They should keep it simpler for end-users, even though they are handling that complexity. They should handle all the complexity, but keep it simple for the end users, so the part they need to improve on is keeping it simple for the end users.

I have been using it in some way, shape, or form for 14 years. At my current place of employment, we have been using it for 8 years.

I would rate the stability a nine out of ten.

I would rate its scalability an eight out of ten.

In terms of the number of users, there are two sides. The number of people who request access would be about 50,000, and there are about 300 or 400 people who do specialized things. That ranges from the actual technical team supporting the solution to people doing more complex business role management and things like that for their pillars within the organization.

We use their premier support. That has differed over the eight years. At the start, it certainly did add a lot of value. At a certain point, about one and a half years ago, One Identity underwent some reorganizations and their support level went down and was not up to our expectations anymore. We have had some serious conversations with them about that. They reacted well because support has picked up back to where we expected it to be. The advantage for us with premier support is that, as a large enterprise, we can always run into specific problems, and, at that point, someone who knows all the ins and outs of the product looks at it and helps us resolve those.

Premier Support has not been an influence in purchasing additional licenses or products from the vendor. However, it has definitely been an influence in using the product for this long and not switching to a competitor.

About two years ago, I would have rated their support a nine out of ten. Given the issues we have had, I would rate it a seven out of ten, hoping it will climb back up to that nine.

Neutral

We have a hybrid deployment model. Technical deployment or technical setup is very straightforward. Integrating it into your entire landscape when it is as big as ours and managing everything is obviously complex. I do not believe that is necessarily due to technology; that is due to the sheer volume of data and applications you need to connect.

From starting the setup to the full global rollout, it took about two years.

It does require maintenance. It primarily includes the occasional cumulative update packs being deployed. The second thing is that we have a constantly changing environment. New applications come in, and other applications are deprecated. We acquire companies. We spin companies off. They are, on the one hand, business-as-usual cases. On the other hand, they do require changes in the system. When you are, for example, suddenly onboarding 5,000 new people because you have acquired a new organization or need to integrate another directory service, then obviously that has some impact.

Our partner is Intragen. Our partner was originally AspisID, and they were acquired by Intragen during the eight-year period.

They helped with the implementation, although it was company-led. We led the implementation, and they provided expert resources. They definitely helped with the speed of the implementation. Some of the things they implemented were good for the initial implementation, but over the eight-year period, it has had some rework, which is not surprising.

We got the training from One Identity themselves which was good. Our partner provided on-the-job training but did not provide specific, in-depth training like a specialized training course or anything.

Our partner was involved in helping us customize the solution for our particular needs. Our experience on the whole was positive. Especially on some very detailed use cases, some choices were made which were good in the short term. In the long term, we have had to revisit them. What we are really happy with is that all the customizations they have done have proven to be very upgradable. Customizations that were done seven or eight years ago are still able to work in the current versions of the product. The customizations were done fairly well within the One Identity framework, but for the specific banking use cases, we are currently revisiting some of those.

The customer service we received from our partner has been very good. They have provided good value. They have definitely helped us move forward. They were originally AspisID and were acquired by Intragen. We have the advantage that they have local people, which always makes for a good collaboration. Their nearshore team integrates fairly well into our organization. They do their best to help bridge the cultural gaps. Due to the way they work with the nearshore team, they have been able to provide the resources we want, which we found to be tricky in the past with the IAM market.

That is a tricky estimate to give. Our primary reason for having the tool is not just a return on investment; without technology like this, we do not see a good way to meet our mandatory compliance requirements. Having a technology like this, whether it is One Identity or another, is almost a given to be able to keep a banking license when you are at our scale. Without it, we would need thousands of additional people. That is hard to translate into a return on investment, other than as a multiple of hundreds. That is just not the way you would tackle that problem.

I am aware of the cost. For us, it is quite cost-efficient. We have a good enterprise license agreement, and we are very happy with what we get for the price we pay for it.

I would compare One Identity Manager fairly favorably to other vendors on the market for identity management governance. We have recently done another RFP and decided to extend our contract, primarily because we have a lot of complex use cases, and the fact that the tool can tackle those fairly well is important for us.

I would recommend One Identity Manager to other users, but I would ask questions like, 'What are the users? How big are they?' For other enterprise organizations, I would definitely recommend it. For smaller organizations, like mid-size businesses with a few hundred employees, I would only recommend it if they are in a heavily regulated space. 

I would rate One Identity Manager a nine out of ten.

My main use case for One Identity Manager is identity lifecycle management, automating user provisioning, access approvals, and de-provisioning across multiple enterprise systems.

A specific example of how we use One Identity Manager is that we automatically create and assign system access for new employees based on their department and role, which removes a lot of manual onboarding work for IT.

The best features of One Identity Manager include that it helps significantly with compliance reviews since managers can regularly certify user access without IT manually tracking permissions in spreadsheets.

The compliance review feature definitely saves time and reduces errors compared to my previous process; before this, access reviews were mostly manual and spreadsheet-driven, so automating certifications reduced a lot of manual error and saved managers a ton of time during audits.

One Identity Manager has positively impacted my organization by improving access governance significantly; onboarding is faster, offboarding is more reliable, and audit preparation takes less manual effort than before.

Onboarding that used to take several hours across multiple systems is mostly automated now, and audit review probably takes fifty to sixty percent less effort compared to our old process.

One Identity Manager can be improved as the biggest pain point is the complexity; customization and troubleshooting can get quite technical, so it takes experienced admins to manage efficiently.

Better documentation with more real deployment examples would help significantly, and the UI could definitely be simplified for day-to-day admin tasks.

I have been using One Identity Manager for one year.

One Identity Manager has been quite stable overall; most issues we have seen were related to custom integrations and our workflow complexity rather than the core platform itself.

One Identity Manager scales well for large environments, especially when mapping and managing thousands of users and multiple connected systems, but performance tuning becomes important as deployment grows.

Customer support for One Identity Manager has been decent overall; response times are usually good for critical issues, but more complex customization problems resolution can sometimes take longer than expected.

Before One Identity Manager, we relied mostly on manual Active Directory processes and a few custom scripts, but it became too difficult to manage consistently as the number of applications and compliance requirements grew.

My experience with pricing, setup cost, and licensing is that licensing can get expensive as the environment scales, and the initial setup took a decent amount of consulting and internal effort, but it made sense for our enterprise requirements.

We mostly use Microsoft Azure as our cloud provider for our hybrid setup.

I have seen a return on investment mainly through operational efficiency; onboarding and access reviews are much faster now, and we have reduced a lot of manual IAM work that previously needed dedicated admin time every week.

Before choosing One Identity Manager, we also evaluated SailPoint and Saviynt, but One Identity Manager fit better with our existing Microsoft environment and customization needs.

My advice to others looking into using One Identity Manager is to make sure you have experienced IAM resources involved early because the platform is powerful but gets much easier to manage when the initial architecture and workflow are designed properly.

One Identity Manager is deployed in my organization mostly on-premises with integrations into some cloud applications, so overall, it is more of a hybrid environment for us.

My additional thoughts about One Identity Manager are that it is a strong enterprise IAM platform if you need deep customization and governance capabilities, but you definitely need the right expertise in place to get the most out of it.

I suggest to others looking into using One Identity Manager that they ensure they have experienced IAM resources involved early, as the platform is powerful but gets much easier to manage when the initial architecture and workflow are designed properly. I would rate this product an eight out of ten.

One Identity Manager is primarily used for identity and life cycle management, access governance, provisioning, and automating joiner, mover, leaver processes across different systems.

One Identity Manager automatically provisions accounts and assigns the right access when a new employee joins. It also handles transfers or adjusts promotions automatically when someone changes roles or leaves the company.

One Identity Manager has been integrated with Active Directory, HR systems, and a few business applications so identity changes flow automatically across multiple platforms from a single process.

The best features One Identity Manager offers are identity lifecycle automation, access governance, role-based provisioning, approval workflows, and risk monitoring and compliance reporting capabilities.

The automation feature is relied upon most because onboarding and access provisioning are much faster now. There have been fewer access-related errors because approvals and role assignments are automated and standardized across systems. One Identity Manager has improved access governance, reduced manual identity management tasks, and helped standardize onboarding, role changes, and offboarding processes across the organization.

One Identity Manager has positively impacted the organization through access governance, reduced manual identity management tasks, standardized onboarding and role changes, and offboarding processes across the organization.

Reporting customization and troubleshooting complex workflows can sometimes be time-consuming, so better visibility and simpler administration tools would be helpful.

One Identity Manager is powerful, but the UI could be more intuitive and some advanced configuration customizations have a fairly steep learning curve.

Reporting customization and troubleshooting complex workflows should be easier and more streamlined, so better visibility and simpler administration tools would help significantly.

One Identity Manager has been used for one year.

One Identity Manager is stable and smooth.

One Identity Manager scales very well for large enterprise environments, especially when managing multiple directories, hybrid infrastructure, and high volumes of provisioning and governance workflows. The platform's modular architecture helps with scaling across multiple domains and millions of identities, although larger deployments usually need careful performance tuning and infrastructure planning.

Customer support for One Identity Manager is excellent, and they are reliable and quick to resolve every query.

Before One Identity Manager, manual processes and native AD tools with some custom scripts were mainly relied upon. The switch to One Identity Manager was made to get better automation, centralized governance, and strong compliance control.

Setup requires proper planning because implementation and customization can take some time in complex environments.

Strong return on investment has been seen mainly through reduced manual identity management work and faster onboarding and offboarding processes. Tasks that previously took hours across multiple teams are now mostly automated, which has improved efficiency and reduced access-related errors.

The pricing and licensing for One Identity Manager are definitely enterprise-focused and can get expensive depending on the number of managed identities and integrations. The automation and governance capabilities justify the investment in large environments.

SailPoint, Saviynt, and Microsoft Entra ID Governance were evaluated before choosing One Identity Manager, mainly because strong hybrid identity governance and flexible provisioning workflows were needed.

One Identity Manager is very powerful and works best when the workflows and access policies are well-planned from the beginning, so it is important to clearly define identity governance processes and role models before implementation. The overall rating for this review is 8 out of 10.

One Identity Manager serves as my primary solution for user lifecycle management, role-based access control, HR-driven identity management, and provisioning and de-provisioning. When a new employee joins, One Identity Manager automatically creates the account and access. When they leave, the access is removed automatically, which maintains security effectively. Role-based access control assigns access based on employee roles and responsibilities rather than manually assigning permissions, which simplifies access management for large environments. Automated provisioning ensures that user accounts and access are provisioned automatically, with access removed or granted based on requirements, reducing manual work significantly.

The best features One Identity Manager offers include central identity management where all user access is managed from a simple and unified platform, reducing complexity and providing great visibility. Strong automation based on user provisioning, onboarding, and de-boarding of employees is another valuable feature. One Identity Manager also provides an audit and compliance-ready environment with detailed logs and reports that help during audit times, which we are using for auditing purposes.

One Identity Manager has positively impacted my organization by significantly reducing the time required for audit preparation and completion. It has improved compliance by ensuring all access is properly approved and tracked. Security has increased, and we now have a compliance-ready environment with improved efficiency. The time for audit completion has been reduced by almost seventy to eighty percent.

One Identity Manager currently offers comprehensive features and is working well for us, providing great features with security and visibility. In some areas, customization could be improved so that clients can customize features based on their business needs.

I have been using One Identity Manager for more than four years.

One Identity Manager is stable.

One Identity Manager's scalability is excellent with no challenges.

The customer support for One Identity Manager is supportive and good in their technical expertise.

I have only used One Identity Manager.

I have had an extremely positive experience with the pricing, setup cost, and licensing because we are receiving very good support from the vendor team.

We are a partner with this vendor.

For return on investment with One Identity Manager, we have seen less effort needed in managing user provisioning or de-provisioning, reducing manual effort by fifty to sixty percent and saving significant time for the IT team. Our audit completion time has also been reduced.

I have had an extremely positive experience with the pricing, setup cost, and licensing because we are receiving very good support from the vendor team.

I did not evaluate other options before choosing One Identity Manager.

One Identity Manager is a reliable solution that is working perfectly for us. My advice for others considering One Identity Manager is to ensure you have a skilled implementation solution resource involved in the project. The solution is powerful and requires proper configuration and understanding, so good planning is key to success in solution deployment. I would rate One Identity Manager eight out of ten overall.

One Identity Manager is primarily used for user lifecycle management, access request and approval, role-based access control, and compliance.

Since we are using One Identity Manager, we have seen a significant positive impact by improving our security through ensuring users only receive the access they need and reducing manual work, making identity management more efficient and organized.

We have experienced specific outcomes with One Identity Manager, including faster onboarding and offboarding processes for users and fewer security incidents.

The best feature of One Identity Manager is the access request and approval functionality, which allows users to request access to a service portal, and the request goes to the proper approver before access is granted, ensuring control and secure access management while also providing a solution that streamlines and assists with audits.

What I find most valuable about the access request and approval features is that they make the environment more secure.

Another standout feature of One Identity Manager is centralized management, which allows all users and access to be managed from a central, unified platform that supports multiple systems such as Active Directory and cloud applications, simplifying identity management.

There is always a need for improvement based on the features, which is why I deducted one point from the overall rating.

I have been using One Identity Manager for more than three years.

One Identity Manager is stable.

Scalability-wise, One Identity Manager is managing our growth of users, so there is no challenge.

I have had a great experience with the customer support team for One Identity Manager, as they are ready to provide support and resolve issues within the timeline.

We have not evaluated other options because we had already decided that One Identity Manager is excellent, so we are using this solution.

I had a good experience with the pricing and setup of One Identity Manager, as the sales team was very helpful during this process and assisted us in implementation, leading to an overall great experience with the pricing and setup cost.

We are a partner with the vendor of One Identity Manager.

We have seen a good return on investment with One Identity Manager, as automation has reduced manual efforts by approximately 40 to 50%, especially in user provisioning and access management, saving significant time for the IT team and reducing the workload of our employees.

I had a good experience with the pricing and setup of One Identity Manager, as the sales team was very helpful during this process and assisted us in implementation, leading to an overall great experience with the pricing and setup cost.

We have not evaluated other options because we had already decided that One Identity Manager is excellent, so we are using this solution.

I highly recommend any organization looking for this type of solution to consider One Identity Manager. My advice would be to plan the implementation carefully and understand your requirements in advance, ensuring your access policies are well-defined for a smooth deployment. I gave this review a rating of 9 out of 10.

I mainly use One Identity Manager for resolving incidents and other tasks, working as both a manager and sometimes as a designer.

We are using One Identity Manager for IGA only, managing the data and identities.

We make use of One Identity Manager's business rules to map company structures for dynamic application provisioning. For the client I'm using, they have multiple business and system rules, so it's going well with a proper structure of business role entitlement and everything.

We are using One Identity Manager for Cloud Azure, but I'm not part of that team as of now.

One Identity Manager helps to minimize gaps in governance coverage among test, dev, and production servers through the CI/CD pipeline, making it easy to migrate the data and development across different environments.

Minimizing these gaps has affected my operations by making it fast. If we automate this process through deployment, then it's very fast.

We are using a DevOps model for One Identity Manager, specifically through CI/CD.

One Identity Manager has helped me achieve an identity-centric zero-trust model because all data related to identity can be seen on the Object Browser, with role and entitlement assigned to that identity along with other relevant details. It's a very good thing as we can view everything about that identity on one page, making it a good approach.

What I find valuable about One Identity Manager is that in the Object Browser, we can see everything, which is a good feature. We can also do and change the data in one place, so that is beneficial; we don't need to query each time.

I find it beneficial because we don't need to open the database, so it's good.

The business rules functionality is important to me because for each individual, we don't need to assign the role. If we assign a particular functionality to the role, it will be assigned to the employee using that business role, meaning we don't need to assign specific things for each employee; it will be done through the business role, which is a good feature.

The main benefits I've seen from using One Identity Manager are that it's very easy to use. I check with other teams, and they are using different tools such as SailPoint and Okta, which are very difficult to learn and manage identities with. With One Identity Manager, the UI is very good; it's easy to learn and understand if we have knowledge about .NET and SQL, or the OOPS concept, making it easy to grasp the tool.

From a user experience perspective, One Identity Manager is good; the only difficulty I find sometimes is because it's a Windows application, it's very difficult to view all data since it's a limited Windows space. Opening multiple windows is difficult as it's a Windows application.

When I need to compare between two different things, I can't do it in a single window. I have to open two windows and check them. Even if I have to change the data, I have to open another instance of the application and check. If it could be done in a single instance, then it would have a better approach.

One Identity Manager has just introduced Angular, so if some of the functionality can be done through a web version, creating a lighter web version to perform tasks would be useful.

I've been working with One Identity Manager for more than one and a half years.

My personal experience with the initial setup and onboarding of One Identity Manager was very smooth. We got training from one of the partners, and we used their online labs to complete the setup, which was straightforward. We did not face any difficulties, and if we follow the proper steps, it's very easy to configure and deploy.

There is very little information available about One Identity Manager on the internet, and very few people are using it, as it's a niche skill. If we could have more information or videos, it would be easier for people to use it, and if we encounter any problems with the tools, we can check the functionalities, understanding what features we can find and where.

I did not escalate any technical questions to the support team, but we have access to labs for a limited period. If we could have lab access extended for more days, it would be helpful for me and my team members to learn more about One Identity Manager, which could assist in related inquiries.

My overall review rating for One Identity Manager is 8.5 out of 10.

My main use case for Identity Manager by One Identity is to onboard and offboard an employee, where whenever a new employee joins, it automatically creates their identity and shares the required access, and whenever someone exits, it automatically disables their account and removes all the access, so it helps in automatically giving access to a joiner and then automatically removing the access whenever they leave.

A specific example of how this automation has helped my team is that whenever a new employee joins, the onboarding team and HR team choose which accesses need to be granted based on their role, and when someone leaves, they revoke all the access. For instance, recently, a tech lead joined, and we had to give him access to many different platforms and accounts, but he disconnected within two days, so we created it on the first day but then revoked it immediately. This does not require much manual checking and also enhances security because employees who are leaving do not have access that was previously difficult to manage as teams were unable to identify all the accesses and some credentials would remain with candidates who were leaving.

Identity Manager by One Identity also helps from a compliance and security point of view.

The best features Identity Manager by One Identity offers include monitoring of identity and providing a centralized system for it, and I particularly value the centralized governance of identity.

Identity Manager by One Identity has positively impacted my organization by reducing the manual identity creation or management work, making all accesses more structured and automated, and by offering clear visibility to the teams during compliance audits due to the structured and clear access visibility.

For example, we have joinings every Monday, and it becomes difficult for the onboarding team to provide logins and create identities manually across different platforms, but Identity Manager by One Identity speeds up that process. The same happens when someone leaves, as the HR team does not have to spend much bandwidth, as they can simply remove all the access of those employees with a few clicks.

Identity Manager by One Identity can improve by simplifying some of the processes, as the environment can be a bit complex when onboarding or creating identities, which requires more in-depth expertise.

There are no specific areas to add regarding making it easier for my team, as it mainly revolves around technical processes that present issues.

Based on my experience, I have not seen any other areas where Identity Manager by One Identity could be improved.

I have been using Identity Manager by One Identity for around 18 months.

Identity Manager by One Identity is highly stable.

Identity Manager by One Identity can scale, and its scalability is strong.

The customer support for Identity Manager by One Identity is good, and I would rate it nine out of ten.

From a ROI perspective, I have seen that fewer employees were needed to monitor governance access, which has also helped in terms of money saved and has brought smoothness and quickness to the system, allowing us to operate quickly rather than manually.

My experience with pricing, setup cost, and licensing is that their setup was manageable, and we did it in-house.

Before choosing Identity Manager by One Identity, we evaluated other options such as Omada and Saviynt, but this is what we have chosen.

For anyone looking into using Identity Manager by One Identity, I would advise that it is a strong enterprise-level solution, particularly for larger teams seeking centralized governance, identity governance, access reviews, and compliance, as it is one of the best solutions available that can help them. I have given this review a rating of nine out of ten.

We use it as it is intended to be used. We have many identities that need to be managed, and we manage Active Directory to handle identity management.

My favorite feature is the visualization. When you open an identity, you can see what is linked to it, such as rules or departments. I really appreciate how you can see things that are connected rather than just viewing them in a list from a database. This is my most favorite feature of the overall One Identity Manager system.

This visualization exists in the backend, and it is also in the frontend, though it is somewhat lacking on our side due to our different setup. However, overall I appreciate all of these features for seeing connected information.

A lot of improvements are coming in the new version, which will improve many things I currently dislike. What I would really appreciate being built upon is dashboards. From what I understand, there will be some dashboards in version 10, but what my colleagues and I would prefer is customizable dashboards similar to Splunk. In Splunk, you can build your own dashboards and set access so that certain people with specific roles can access particular dashboards. You would have some presets, but you could build it like a puzzle for what you need and what you prefer. This customization capability is currently lacking.

I have been using this solution for two and a half years.

Stability could be improved. Our infrastructure for One Identity Manager is quite large, and there are many potential pain points. The infrastructure is complex with a lot of built-in components, and anything could be causing the issues. We have accumulated so much that finding out what is causing the problems is sometimes difficult in itself.

Our scale is quite large, and I would confirm that One Identity Manager handles this.

I have not personally contacted customer service, but I have heard from colleagues who did, and they were not happy about the support.

Negative

I am currently in the phase of initial deployment on a new infrastructure, and I would say it is acceptable. It is not the worst, nor the easiest.

This project has been ongoing for approximately one month, and I am still not complete because it is only about job servers. The main problem is that we have many customers that we need to connect to. Each customer and each connection is different, which is the biggest pain point.

This implementation requires a lot of maintenance.

I would say it requires a lot of operational work, and since we have many requirements, we also need to develop a lot of custom components that are not included out of the box. It requires significant initial maintenance to build something, then follow-up maintenance when migration happens, and you need a lot of maintenance if there is data inconsistency and then a lot of changes.

I cannot really answer this question because I have not been involved with the SAP aspect. Could the question about maintenance as infrastructure or the software and managing be more precise?

I know we have a connection, but I think we are not using the out-of-the-box connection.

One Identity Manager is used to automatically handle user accounts, passwords, and access permissions across our entire company from one central place. When new employees join the company, this system automatically creates their email, sets up their accounts, and grants them access to the exact folder they need for their job on day one.

The best features One Identity Manager offers are automated workflows for onboarding new hires, the self-service portal where employees can request access to applications, and the clear reporting tools for security audits.

The automatic workflows and the self-service portal make my job easier and more efficient because the self-service access request allows employees to ask for the software permissions they need, routes the request to their manager for approval, and grants access automatically without IT having to do it manually.

One Identity Manager has positively impacted my organization by drastically reducing the time it takes to onboard new employees and helping us in security audits because it tracks exactly who has access to our data.

The time saved during onboarding is approximately 40 to 50% because previously it took considerable time; now the system automatically provisions accounts based on HR data, which significantly reduces our manual setup. Regarding security audits, it saves our time due to the real-time logs present, allowing us to track everything and later fetch it to create a report.

One improvement could be a focus on documents, specifically an official document for the advanced troubleshooting guide so that anyone can understand and troubleshoot effectively.

I have been working in my current field for more than three years.

One Identity Manager has been discussed thoroughly regarding potential improvements. My advice for organizations considering One Identity Manager is to focus on planning and strategy, spending considerable time cleaning up your company's active directories and foundational HR data before starting the implementation because the solution is very powerful, but you have to clearly define the policies and utilize automation. I would rate this product a 9 out of 10.