One Identity Manager Reviews

I have worked on various European projects where we mainly use this tool as an Identity and Access Management (IAM) solution rather than its Privileged Access Management (PAM) features. Specifically, it serves as a central IAM tool for governance, compliance, and managing access requests across all the companies and projects I've been involved with. Most of these access requests were processed through Microsoft tools. They were onboarding applications and managing access to them via One Identity Manager through the portal it offers.

Every identity management tool has its unique features, and I believe that One Identity Manager performs quite well. From a developer's perspective, its interface provides excellent information. It includes appealing visuals and a user-friendly design, allowing you to clearly see how software accounts correlate or match with an identity. This gives you a comprehensive view of what an identity encompasses. You can establish specific rules to determine if access is fully managed by One Identity, which acts as the authoritative source for system access. Additionally, it offers a range of capabilities and customization options for managing access across various applications. Overall, I think One Identity Manager does a commendable job in this area.

One Identity Manager can be set up to have accounts synced from the SAP system and have them as orphaned in the system. The intended way is to link them to an identity, and when clicking the identity of the employee, you will see underneath the AD accounts, other application accounts, and different SAP accounts. For each SAP system, you can have specific rules. It has this capability out of the box, SOD rules, different roles, and bundles.

When users request access for a SAP system and do not have an account already, an account is created based on specific criteria that can be defined. From an end user point of view, they go to the portal and request access. If they do not have an account, they get one. If they already have an account, the access will be added and provisioned properly. The account will be connected to their identity with all the access in the downstream application in SAP. It requires a good architect to think through all the different cases for the business. Many connectors must be built because some companies use upwards of 200 SAP systems.

One Identity Manager offers governance for cloud apps through its cloud framework. The logic remains similar to on-premise applications: build a connector, import data, create business roles, enable requests, and implement approvals. The governance framework is particularly strong with application approval workflows and recertification processes.

The solution provides technical options to distinguish between different types of accounts per system. For AD, different rules can identify and manage various account types differently. It offers strong reporting capabilities and can detect policy violations.

For application management, One Identity Manager has a built-in risk framework that helps businesses with approvals and recertifications. Full application management without IT involvement requires building custom frameworks.

It helps to streamline application access decisions, application compliance, and application auditing for customers. When auditors come in, they require that access be managed using an IGA tool. It's quite easy to set up; you just need to build a connector to facilitate this access. In addition, a business analyst can identify the business rules needed. You publish the business rules and set up an approval process—usually requiring two approvals if it's related to the application. Once the business rule is published, a user can request access through the portal, and someone will approve it—standard procedure. You can also run certifications and set up different approval processes for employees who need access for one year or for those who are moving (like shifts). Certification can involve various terms, including access reviews or access refusals. It's a straightforward process. It's strong and reliable. I've seen hundreds of applications successfully managed and compliant because of this process, which includes approval requests and access refusals. You simply onboard the application, and you're set—it all becomes remote for you. All the audit trails are available. You can see who approved what, why they approved it, when the access was granted, and when it was revoked, among other details. It truly helps to maintain compliance.

The solution offers some out-of-the-box capability to manage profiles, but I have not worked with other aspects. In the companies where I was working, they were not using this from a SAP point of view.

One of the most significant advantages is its strong security around identity management when compared to other tools; it's quite robust. However, it does come with a high learning curve, making it difficult to implement and operate without a dedicated IAM team. You need people with substantial experience—likely several years—in order to navigate the complexities effectively. It's not something you can easily outsource entirely to a consultancy. In the past couple of years, they released a new version, Version 9, building on the previous version 8.02. This new version introduced a revamped portal where end users can request access. The previous version had a built-in portal that was quite complex to configure. In the new Version 9, they developed a new portal based on Angular, which offers many capabilities. If someone knows how to utilize it and learn its features, they can make API calls to interact with other systems. Some consulting firms are already developing custom frameworks around this to leverage these capabilities. 

This new portal is where end users go to request access. It provides good out-of-the-box functionalities, allowing users to request access to various applications, and managers can approve these requests. In addition to the default functionalities, the use of APIs is enabled through the portal. However, the general market lacks expertise regarding this tool; only a few companies are actively investing in understanding how it works and offering their services based on that knowledge. Many businesses are migrating to this new portal as the older versions are being phased out of support and are eager to learn how to maximize its capabilities.

Overall, One Identity Manager is a robust tool designed for large enterprises and is still an on-premise solution.

One Identity Manager does not offer much in terms of delivering SAP-specialized workflows and business logic. Custom workflows can be built, but it is limited in that regard. Comparing it to SailPoint, One Identity Manager is less advanced around SAP, particularly regarding the flexibility to build custom flows. While customizations are possible through processes in One Identity Manager where you can build PowerShell code or make API calls, this is not the intended way and requires heavy customization that might become unmanageable.

They could offer more out-of-the-box connectors so that custom PowerShell connectors would not need to be built. 

The support could be improved. They could add more AI to help with role mining. The new portal documentation needs improvement as some partners are more advanced in understanding how the Angular portal works than One Identity itself.

I'm not currently working with it. I stopped working with it three to four months ago. Before that, I worked with it for about three years and seven months.

Regarding support, they prioritize resolving escalated issues. However, their response can be slow. Whenever I open a ticket, the reply often includes a request for the specifications of the server I am using. For instance, they frequently ask, “How many gigabytes of RAM are you running on the server?” If I'm not using the maximum recommended specifications, they immediately suggest that there is a problem. They don’t always consider that the issue may not be related to performance at all.

I haven’t had the best experience with them, but I understand that they do eventually respond. However, there have been instances where we had tickets open for months without any resolution. Sometimes, they would either go quiet or eventually respond and help us find a solution. I’ve faced many similar situations across various projects.

At the end of the day, I’m not a customer, so I’m not too concerned about the experience. However, the application owners of One Identity in these companies have expressed dissatisfaction with the responses they received. They wanted more immediate assistance and access to more skilled resources. That's understandable. Overall, I would rate the experience as a six out of ten.

It depends on the situation. If you're starting from scratch, in a greenfield scenario, where you have nothing set up and don't have an IGA tool, then you can begin by establishing an Active Directory. You start with the basics: take employee data and import it into One Identity Manager to create Active Directory accounts for each employee. This setup can typically be completed in about three to four months. It’s not overly complicated. However, it’s important to note that most businesses have complex processes that don’t easily translate into the tool. To effectively monitor applications and manage these processes, you really need technical expertise.

For a large enterprise that has the capability to support an on-premise solution and is willing to find reliable partners to assist with this new portal, along with the technical know-how to match the tool's capabilities, it can be a highly effective solution. This tool offers a wide range of features out of the box. However, the biggest challenge is the steep learning curve; it's essential to have experts with many years of experience and strong technical expertise to maximize the tool's potential. This solution is not suitable for small companies or those seeking a quick implementation. It requires a significant investment initially, but it pays off in the long run due to its extensive features compared to other tools.

I don't have information on the costs associated with the tools or the specific deals they offer. However, I do know that it's challenging to find technical expertise, and these professionals often command high salaries.

In addition to purchasing the tool and its licenses, it's important to account for the need for a dedicated team, especially if you're a large enterprise. There are significant costs involved in maintaining the solution and ensuring it operates effectively. Unfortunately, I don't have details on the licensing fees or per-user costs, among other specifics.

My recommendation is that you really need to understand the realm of identity and access management. It's important to consider the alternatives available, and I believe that for some companies, One Identity is the best solution out there. For specific enterprises, it could indeed be the ideal choice, but for others, it may not be suitable. For instance, a small business with fewer than 25,000 employees, which may not prioritize governance and compliance, might find One Identity unnecessary. It really depends on the landscape of the company using the tool—what their requirements are, what applications they have, and what they're aiming to achieve.

One Identity is quite beneficial for finance-related entities that have strict compliance and security needs. However, One Identity should invest more in AI and enhance their documentation on the new portal. This improvement would help customers and developers better understand what they are building.

The business roles functionality is a very standard part of the access model. Typically, you would start with an application. You gather all the users and their entitlements, which include the accesses they have. Then, you need someone, such as a business analyst or consultant, to help identify bundles or groups of this low-level access. Instead of managing each access individually, you can group them together and create a role for each application, or possibly a combination of different applications. This approach greatly simplifies management. A user doesn’t need to know all the low-level accesses required in a system or across different systems. By creating bundles of access with accompanying business rules, it becomes easier to understand. For example, if I am a DevOps member working with AWS, there’s already a pre-defined access bundle for me. My colleague can tell me to request this specific access, which provides everything I need. Alternatively, access can be automatically assigned based on department—whenever someone joins a specific department, they receive all associated accesses. 

Moreover, you can build dynamic rules around these business rules. While technically speaking, in the One Identity Manager, an application role is part of a business role. However, it’s important to note that you can have a business role defined by specific criteria. Anyone who meets this criterion receives the business role, which is beneficial for management. For instance, if you want to grant access to new hires for applications like Teams, all relevant accesses can be bundled into a business role. If someone leaves the company, their status would change to inactive, and they would lose their access. This streamlines the access lifecycle management process.

From an end-user perspective, it simplifies requests for specific applications or accesses per department. Depending on your chosen architecture and access model, this organization is crucial. However, a key requirement is to have a business analyst involved; otherwise, you risk ending up with scattered entitlements and groups that lack clarity regarding their business association. Finally, don't forget to set up an approval process.

From an end-user perspective, with the new Angular portal in version 9 and upwards, it has improved significantly. However, not all companies have migrated because they have custom logic in the old portal that needs to be translated to the new Angular portal. The new portal is better as it is easy to navigate with straightforward navigation bars. Previously, sometimes custom queries behind the portal really slowed down end-user performance, with users reporting waiting 15-20 minutes for a page to load, especially during approvals or attestations. This was particularly frustrating for users needing high-level managerial approvals for various tasks. In the new portal, you can customize tasks to address some of these performance issues, making it a more efficient experience.

Overall, I would rate it a seven out of ten.

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.

Positive

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 are using One Identity Manager to change our previous old identity access management platform. Currently, the separation of duties is the most important aspect.

It delivers SAP-specialized workflows and business logic. It meets the needs of the most common use cases. It also supports customization for special cases.

Its biggest benefit as well as its biggest problem is that it is highly customizable. Usually, customers do too much customization, and then it is not great performance-wise.

We started to see how to optimize or support audit processes with One Identity Manager about a year ago. It has been helpful there. It saved quite a lot of time.

It did not help us to achieve an identity-centric Zero Trust model, but that is because we need more push from the business or management.

It helps automate processes. Our company uses One Identity as an enabler, which would be nice to change. It helps us save on license costs through effective license management.

It is highly customizable, a feature that influenced our company's decision. We can easily customize it.

I find it user-friendly. Once you have some experience, it demonstrates best practices and guides you on the correct way to use the tool. 

Default connectors work fine, but certain connectors, such as SCIM to SAP Cloud Identity Services connector, have quite a few bugs. They are not so great.

Their support can be better. They can also improve testing of their product before releasing new versions. We have had a few critical issues after upgrading to a newer version, which also caused problems with auditing.

Our company has been using One Identity Manager for around seven years, but I have personally used it for four years. I became its developer four years ago.

We are using it at one location. We have about 30,000 active identities. We have five people working with this solution.

There is room for improvement. For each ticket, they require logs or traces from the system, even when the issue shows no logs. This requires sending the information back and forth, which consumes a lot of time. After submission, they contact the product team, which often takes one or two months to respond.

Neutral

I have not worked with other solutions.

I was not involved when they started implementation, but it was complex. This complexity was not due to the difficulty of implementing One Identity Manager, but rather a lack of business support for our process decisions.

Deploying the One Identity Manager solution itself is easy. The documentation is clear.

You can do customizations. It can be customized, but it is hard to customize correctly without affecting the system.

IPG is our partner. They have helped customize the solution for our needs.

Their support was alright. It is important that the partner advises to follow the standards because customizations can cause issues. It is better to change the process instead of going for customization.

We received very good support from them post-implementation. It is of high level. I would rate our One Identity Partner a ten out of ten in terms of value.

I would recommend One Identity Manager for sure. It is quite easy to use as long as you find a good partner who can facilitate changes in the process rather than customize it for every single case. Many issues arise from the misuse of the system due to extensive customizations. If used correctly, there would be fewer issues, and it would be a fast, quick system.

It can be a bit complex to learn for new users when there is a lot of customization.

It has a lot of potential. We try to use it as much as possible, but we are not using it to its full potential. The problem is business support. 

Overall, I would rate One Identity Manager an eight out of ten.

We use One Identity Manager for access management and provisioning, as well as onboarding target system applications. It focuses on identity management and providing access. 

We use different tools like Web Designer and Synchronization Editor, and we do implementation, customization, and configuration based on our requirements.

I can see many benefits, including granting the right access to the right people at the right time. It helps with enhancing security, validating identity types, and assigning initial rights based on the defined processes. Users follow request workflows inside the system to access, which is validated for correctness.

We use One Identity Manager to manage SAP target system applications. We generally use the SAP connector. We create the SAP onboarding project in Synchronization Editor. It is like a bridge between One Identity Manager and the target SAP system applications. It is able to meet our requirements.

It has had a Windows-based UI, and they are also moving to a web-based portal. One Identity Manager helps manage identities and accounts, and we can also see the pictorial representation of the identities there.

We do a lot of customization. It supports customization based on our needs. However, when it comes to Web Designer, customization can be a bit challenging.

We have onboarded 30 to 40 applications, including SuccessFactors, ServiceNow,. We are about to complete SuccessFactors' integration with One Identity. Previously, we used to get the identities in the form of a CSV file where the data was inserted inside One Identity to create the identities of new joiners and do the onboarding. It is now connected to the SuccessFactors application. It is also integrated with ServiceNow. If any incidents get raised, they can be routed to the respective operations or engineering teams for resolution.

One Identity Manager helps minimize gaps in governance coverage among test, dev, and production servers.

One Identity Manager helps streamline application access decisions, application compliance, and application auditing. We have dedicated teams focused on compliance and auditing.

One Identity Manager has helped us achieve an identity-centric Zero Trust model.

In One Identity Manager, I appreciate the Synchronization Editor for onboarding different target system applications. We have various connectors that allow customization. For instance, the Windows PowerShell connectors can connect to different services such as RESTful services, SOAP services, and Windows services. I like how data flows from the target system applications to One Identity. We explore technical aspects, write functions in PowerShell, and connect with APIs. 

Another interesting feature is attestation, where we review and re-attest existing employees' rights. We create attestation policies, workflows, and schedules.

A major area for improvement is Web Designer. If One Identity Manager advances this, it will greatly benefit all customers. Web Designer is based on legacy Microsoft technologies like ASP.NET and HTML. I believe future improvements will resolve performance issues.

I have been using One Identity Manager for the last six years.

It is stable but need more improvements.

It is scalable. I would rate it an eight out of ten for scalability.

We use their regular support. Could be rate 7 or 8 out of ten.

Positive

We do not handle the initial setup, but from what I have heard, it is not complex.

In terms of maintenance, mostly it requires monitoring and health checks to ensure everything in the infrastructure is working properly.

I would definitely recommend One Identity Manager. It offers many opportunities for technical learning, implementation, and customization. One Identity Manager is a good solution for identity and access management, provisioning, and other IAM aspects. 

I would rate it an eight out of ten.

We use One Identity Manager for user lifecycle management and access management.

Since I am placed in the business organization, I see smooth processes for joiner, mover, and leaver, and a compliance perspective. We are getting cost savings by automating system integrations. Previously, people handled access rights manually for each system. Now, after integrating about half of our systems, we are saving approximately three FTEs, and expect it to double. Line managers can see team members' access rights and do attestations in one view. We have integrated requesting of access rights also to external systems via the web portal to remind leaders about access rights management also for leavers and movers. Automation of these processes improves security and compliance by meeting auditor requirements.

There are functionalities we needed to build ourselves, such as cleaning the direct entitlement assignments if inderect exists. The user interface can sometimes be a bit confusing for end users, for example during attestations, as completed tasks simply disappear without indicating that there are no pending requests left any more and therefore end-user is unsure if they have completed all theirs tasks.

We have had it in production since autumn 2023, approximately one and a half years.

I rate stability around nine out of ten.

We have around 8,200 employees using the system to request access rights. Scalability is not an issue, so I rate it a nine out of ten.

I rate customer support at eight out of ten. The response time has room for improvement as it can take quite a long time in some cases.

Positive

Previously, we used an old Microsoft MIM solution. We transitioned to One Identity Manager for improved functionalities like handling mover situations and integrating external systems for better security compliance.

We implemented it through Tietoevry, a partner. Initially, we had an unsatisfactory experience with a different partner, which delayed our project by a year. After switching to Tietoevry, the project improved significantly.

Annually, we have saved three full-time employees as a result of deploying One Identity Manager. We anticipate doubling this saving once all current integrations are completed and even more when we add Segregation of Duties rules.

I would recommend One Identity Manager due to the improved security and compliance it offers. We have achieved considerable productivity gains through automated processes. I rate One Identity Manager a nine out of ten.

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.

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 for identity and access management most often. One Identity Manager is used to identify employee data and provide access according to employee seniority. Privileged access is also managed through One Identity Manager to grant specific access to employees according to their roles.

One Identity Manager offers an easy-to-use interface, integrates with apps, and is scalable. These are the three major useful features.

The easy-to-use interface of One Identity Manager is rated at the top priority. If the software is not easy to use or user-friendly, then the major purpose of the software is not served correctly. The user-friendly interface is the main feature relied upon most and represents the unique selling proposition of One Identity Manager.

One Identity Manager has impacted the organization positively. The easy-to-use interface has reduced time and increased efficiency. The software also provides flexibility to give access to employees according to their roles, which has streamlined role management.

Productivity has definitely increased with One Identity Manager. Approximately 20 to 24 hours of employee time are saved each month, which has increased the efficiency of employees and has overall impacted revenues positively.

The reporting in One Identity Manager needs to be improved, as some of the data sets obtained from reporting are not very user-friendly. Email integration is also not working properly and needs to be more user-friendly for users who are from a non-technical background.

Minor glitches in One Identity Manager need to be improved, and the software needs to be sped up. There are some lags that need to be addressed.

One Identity Manager has been used for the last one year.

Minor glitches in One Identity Manager need to be improved, and the software needs to be sped up. There are some lags that need to be addressed.

The customer support from One Identity Manager has been positive. The customer support provided is quite good.

Negative

Productivity has definitely increased with One Identity Manager. Approximately 20 to 24 hours of employee time are saved each month, which has increased the efficiency of employees and has overall impacted revenues positively.

One Identity Manager is a good choice for those looking for identity management software with a user-friendly interface and good customer support. One Identity Manager is also a cost-efficient solution for those seeking an affordable option. One Identity Manager has been rated an eight out of ten. The user-friendly approach of the software and the customer support received are the main factors behind this rating.