OneLogin Customer Identity

My main use case for OneLogin Customer Identity by One Identity is that I was one of the administrators of it, besides also using it as an employee of the company. I was assisting in user and application provisioning, as well as troubleshooting for those.

A specific example of how I used OneLogin Customer Identity by One Identity in my admin role involves using an external multi-factor authentication like Duo as my MFA. One instance for user account troubleshooting involved creating the user account where I needed to unregister the MFA factor and ask the user to re-register again in order for OneLogin Customer Identity by One Identity to pick it up and exchange a new token, making sure it was now validated. From an application side, I was also using OneLogin Customer Identity by One Identity to integrate for single sign-on. For example, users who needed Adobe access, I would go into the Adobe application and create a linked connection to OneLogin Customer Identity by One Identity. OneLogin Customer Identity by One Identity already had the pre-setup out of the shelf that I could connect. From there, I would set up the callback URL and choose for SCIM provision and de-provision, so users would automatically receive a license assignment and be assigned Adobe at the time. Users would jump into their main OneLogin Customer Identity by One Identity page and from there they would just navigate and browse through the listed applications and sign in to whatever they needed.

OneLogin Customer Identity by One Identity was my main tool, so everything was behind OneLogin Customer Identity by One Identity. Even for in-house applications, for example, with LDAP authentication or some other type of authentication, I would put it behind OneLogin Customer Identity by One Identity so that it was more secure and more reliable in terms of a token exchange and user authentication and authorization. I was having OneLogin Customer Identity by One Identity as my main tool and it was hosting thousands of applications within my company.

The best features OneLogin Customer Identity by One Identity offers are those that come out of the shelf.

The out-of-the-shelf features and the application onboarding in OneLogin Customer Identity by One Identity include thousands of applications. Whenever I would look for an application, I could connect to it and find the proper way to connect and put it behind OneLogin Customer Identity by One Identity. Even for those that didn't have a pre-established connection, it would be easier with the documentation from both sides and OneLogin Customer Identity by One Identity support to onboard the application and make the right connections between it.

OneLogin Customer Identity by One Identity has positively impacted my organization because it brings a more secure and reliable way for users to access applications. Besides also the easiness of a user who may not be super savvy to go to only one page and then be able to browse through everything, it not only reduces friction in the support between providing access and troubleshooting access for applications, but it also takes the knowledge team itself in building a more secure environment.

I am not sure if there were any enhancements in terms of AI or any other features added, but when I used OneLogin Customer Identity by One Identity, it was a very good product. Regarding improvements, I think it is simple enough for users to understand it.

I have been using OneLogin Customer Identity by One Identity for three years in the past.

OneLogin Customer Identity by One Identity is stable. I recall experiencing a couple of flaws over the course of three years, but nothing major that impacted the company heavily.

OneLogin Customer Identity by One Identity's scalability is excellent. When I first joined the company, it had around 6,000 users when OneLogin Customer Identity by One Identity was onboarded, and at some point, I was dealing with more than 15,000, so it doubled in size and it still was handling fine with no gaps or issues.

Customer support for OneLogin Customer Identity by One Identity is easy to reach. Every time I needed anything, they were very quick and I could solve things within a maximum of a couple of hours.

OneLogin Customer Identity by One Identity was my first solution; I did not have any before.

Integrating OneLogin Customer Identity by One Identity with my existing applications and infrastructure was very easy and very straightforward. The documentation was pretty clear, so I did not experience any major issues.

I would say that once OneLogin Customer Identity by One Identity was implemented, it reduced tickets, especially for passwords for users that were struggling to get into some application since everything was behind it.

Before choosing OneLogin Customer Identity by One Identity, I evaluated other options such as Okta. Although Okta had some different capabilities, it was decided that OneLogin Customer Identity by One Identity had the best features that would fulfill the company's needs.

The learning curve for new administrators or users of OneLogin Customer Identity by One Identity is straightforward. It is no rocket science. For users, you could get used to it from the get-go after switching. From an admin perspective, once you get the user, the administrator or IT team to understand how everything works in the backend in terms of onboarding users and distributing the right amount of access for each team, then you stop experiencing any issues and it works very well.

OneLogin Customer Identity by One Identity handles compliance requirements in my organization well, especially for GDPR. I was able to understand where the data was being stored, how I could retrieve it, and who to reach out to in case of deleting.

The performance and speed of OneLogin Customer Identity by One Identity during peak usage times is outstanding. The service was probably very well deployed, and the users overall did not experience any slowness even during peak hours, such as business time zones. I did not get any complaints or anything that would stop the user from working their day-to-day business.

Customizing OneLogin Customer Identity by One Identity to fit my organization's specific needs is very easy. At least the version I had, I recall there was a configuration page where I could change the banners and colors and put my company logo, so it was not hard.

I manage user roles and permissions within OneLogin Customer Identity by One Identity by connecting it to my Active Directory. At the time, I was actually using a different directory for permissions, so OneLogin Customer Identity by One Identity was pushing groups and permissions from there, but it did a good job as I could just capture and not really apply restrictions on roles that I created within Microsoft. That worked quite as a built-in feature.

OneLogin Customer Identity by One Identity supports multi-factor authentication and single sign-on for my organization by being flexible for the user in terms of using either Google MFA or Duo. Sometimes I force the use of Duo as my MFA. Although I understood that OneLogin Customer Identity by One Identity has its own multi-factor authentication, I cannot recall the outcome when I tried to use that feature from OneLogin Customer Identity by One Identity.

I would rate this review as a 9 out of 10.

My main use case for OneLogin Customer Identity by One Identity is that as a support analyst and part of the consulting team, we mainly use it for services integrating into corporate environments, integrating MFA and SSO for some companies that need access control, both to unify accesses within a company for a person, make it easier for the person to access several applications they use in their daily life, optimize their time, make their access easier, and control these accesses. We have several authentication factors where you can ensure your company is not being hacked, from the user with the lowest privilege up to the most privileged user possible.

A specific example of how this MFA and SSO integration helped a client is when a company had many employees that needed to control their access and unify their accesses because the HR team, for example, needed to access the HR app, the HR system, their email, Canva, spreadsheets, and various other applications every day. Each application had a login and password, so for the person to keep remembering them, many wrote them on Post-it notes and left them on their desks, others had a notepad file saved on the computer. This was a big headache for the company, and they wanted to avoid it because they could face a breach, which could harm the company since the HR team controls the company's financial side. SSO and MFA were integrated effectively in this situation, helping employees have less friction in their daily routines, so they did not need to memorize login and password. They could set a more robust password that was harder to crack, and at the same time, there was security around this with MFA, with the authentication factors that helped a lot with the service for the client.

The best features that OneLogin Customer Identity by One Identity offers are multi-factor authentication, Single Sign-On, SSO, and Vigilance AI. I consider the artificial intelligence embedded in the accesses via Smart Factor to be very good, as well as the roles features, which are easy to configure, along with the mappings and their integration. It has broad integration with various applications, whether with SAML 2.0 certification, OAuth, or OIDC, so there are easy configurations in case the application is not present in the library, but the library is also very extensive. These are very positive points, in addition to the many directory connections, whether to a Windows directory such as Active Directory, or directories on Linux machines, or an HR system, making it a simple, easy implementation that can be clearly explained to the client, and the features it proposes to deliver are very good.

OneLogin Customer Identity by One Identity has had a positive impact on my organization because it unifies all accesses, being a platform, and is a SaaS that is easy to implement, organized, with a very practical visual interface. You can access things easily, and by paying attention to what you are handling, it is easy to configure things and keep the system secure, which makes life much easier for both the engineer, the support analyst, the consultant, and for the end user. Although I cannot bring a specific result or metric demonstrating this positive impact, I know that almost half, if not half, of the tickets opened by the team for the IT team or Help Desk are password resets. Once OneLogin Customer Identity by One Identity resolves this with self-service password reset, the person can do their own reset without needing to open a ticket, which relieves the IT team and Help Desk, allowing them to focus more on larger projects, consequently saving money for the company due to simple password resets.

The only detail is more on the financial side; its licensing ends up being very expensive, and the per-user licensing campaigns are a bit pricey. Depending on the region, the company, and the type of contract you are trying to establish, it ends up making the price a bit high for companies to close deals. We struggled a lot and are still struggling because many clients are very interested in the solution, but when it is time to talk to the sales side, things fall apart. The user pricing ends up increasing significantly because many companies have more than 1,000, 2,000, 5,000, 10,000 users and up, making licensing a roadblock.

My experience with pricing, setup costs, and licensing is a bit negative because, although the solution is amazing and a very good system, the prices are a bit exaggerated, especially at larger scales. At our company, we have been trying to close contracts lately, but we always face the same financial problem; companies like the solution a lot, but they do not adopt it due to the price. It is very high compared to market competitors, and since it is a system that is a bit different from what the market is already used to, it is difficult to compete with a price that matches competitors. Moreover, for larger numbers of users, the price per user stays the same, which impacts budgeting and negotiations negatively.

I have been using OneLogin Customer Identity by One Identity for around a year and a half.

OneLogin Customer Identity by One Identity is stable. During my experience of one year and a half, I faced very few problems, difficulties, or system downtimes, with at most about twice where the server went down, but it was back up the next day.

The scalability of OneLogin Customer Identity by One Identity serves very effectively and works perfectly. It handles all user numbers, whether small, medium, high, or increasing, very effectively. Because it is a cloud solution, it has much easier implementation and control, making scalability a smoother process.

Customer support for OneLogin Customer Identity by One Identity in Brazil is still a little behind. I know they are in some transition processes, expanding and building a larger team for support; they are just now entering Latin America and starting to grow. Although we have not faced any very big problems, their support is not very fast. We managed to solve most issues we faced easily, but there was some delay.

We have not used any other market solution similar to OneLogin Customer Identity by One Identity, so there is no previous solution to discuss.

OneLogin Customer Identity by One Identity is currently deployed in the public cloud, using a customized license, because we only use it to build demo scenarios. We do not actually use it for our company's daily accesses, but we use it to demonstrate it to clients in real use cases or PoCs.

We use the native provider from One Identity for OneLogin Customer Identity by One Identity, as it is a SaaS, entirely in the cloud, hosted in One Identity's systems.

Unfortunately, I cannot share any return on investment or relevant metrics related to time savings or reduction in tickets because, at our company, we have not implemented OneLogin Customer Identity by One Identity effectively; we only have a customized version for building presentations.

My experience with pricing, setup costs, and licensing is a bit negative because, although the solution is amazing and a very good system, the prices are a bit exaggerated, especially at larger scales. At our company, we have been trying to close contracts lately, but we always face the same financial problem; companies like the solution a lot, but they do not adopt it due to the price. It is very high compared to market competitors, and since it is a system that is a bit different from what the market is already used to, it is difficult to compete with a price that matches competitors. Moreover, for larger numbers of users, the price per user stays the same, which impacts budgeting and negotiations negatively.

I did not evaluate any other solution before choosing OneLogin Customer Identity by One Identity; since I joined the company, we have already been working with and thinking about implementing One Identity products, mainly OneLogin and Active Roles.

My advice for others considering using OneLogin Customer Identity by One Identity is that I would easily recommend it. It is a solution that delivers what it promises, easily accomplishes what it sets out to deliver, with straightforward implementation and very good scalability. Given that it is a SaaS system, you will hardly face outages or disruptions, and it has straightforward applicability; it serves its purpose with a simple implementation. Overall, I would recommend it a lot.

I liked the interview a lot, but I think it could have been a bit faster. It took a bit too long, but overall it was very interesting, conducted effectively, and it made it possible to understand the needs. I gave this review a rating of 9 out of 10.

Our main use case for OneLogin Customer Identity is for employee access management. When a new employee joins, we set them up in OneLogin so they can securely access all our internal apps with just one login. This has simplified onboarding and kept everything secure.

We also use OneLogin Customer Identity to integrate with some third-party tools. Having everything tied together is convenient, so our team spends less time logging into separate systems and more time being productive.

The best features OneLogin Customer Identity offers are identity management, single sign-on because it saves a ton of time, and multi-factor authentication, which adds a strong layer of security. I really appreciate how easy it is to set up and manage groups and permissions.

Single sign-on really streamlines things. Our team logs in once and they get instant access to all the apps they need, which cuts down on password fatigue. Managing groups and permissions was a smooth process overall, but we did have to spend some time initially planning out the group structure to avoid overlap. Once it was set up, it has been really efficient.

The reporting and analytics are super helpful. We can see who is accessing what, when, and spot any unusual activity. This gives us a solid overview of how our team is using their support.

OneLogin Customer Identity has had a very positive impact on my organization. The biggest benefit has been improved security and better access management. Before using OneLogin Customer Identity, managing user accounts across multiple applications took a lot more time and effort. Now, with centralized authentication and single sign-on, our employees can access the tools they need quickly and securely. It has also reduced the number of password-related issues and support tickets, which saves time for both our IT team and end-users. From a security standpoint, features such as multi-factor authentication give us great confidence that only authorized users can access our systems. Overall, it has helped us improve operational efficiency, strengthen security, and provide a better user experience for our team.

I had a positive experience overall, but there are a few areas where I think OneLogin Customer Identity could be improved. One area would be the initial setup and configuration process. While the platform is powerful, some of the advanced settings can be a bit complex for new administrators, and more guided setup options would be helpful. I would also appreciate more customization in reporting and dashboards. The existing reports are useful, but having additional flexibility to create custom reports and visualize data would make it even more valuable. Another improvement could be expanding the documentation and troubleshooting resources for advanced integrations. Most integrations work well, but when dealing with more complex environments, more detailed examples and best practices would help speed up implementation. These are relatively minor points overall. OneLogin Customer Identity has been really secure and easy to manage, and we are satisfied with the results.

Another area of improvement would be the user interface and the mobile experience. The overall interface is clean and functional, but some administrative sections can feel overwhelming, especially for new users or administrators who are not familiar with the identity management platform. These enhancements would be an improvement.

I have been using OneLogin Customer Identity for about six months now, and it has really helped us streamline user access. It has been reliable for both multi-factor authentication and single sign-on.

My advice to others looking into using OneLogin Customer Identity would be to start by clearly defining your identity and access management requirements. Before implementation, take time to understand your user groups, applications, access policies, and security requirements, as this will make the deployment process much smoother. I would also recommend planning your role and group structure carefully from the beginning. A well-designed access model can save a lot of administrative effort later and make onboarding, offboarding, and permission management much more efficient.

Another recommendation I would provide is to take full advantage of features such as single sign-on, multi-factor authentication, and automated user provisioning. These capabilities provide some of the biggest benefits in terms of security, user experience, and operational efficiency. Overall, OneLogin Customer Identity is a strong solution for organizations looking to improve security and simplify access management. If it is implemented with proper planning and governance, it can deliver significant benefits in both security and operational efficiency. I would rate this product a nine out of ten.

My main use case for OneLogin Customer Identity involves addressing the integration of applications and resolving access issues that customers may experience. If customers face access problems, we must reach out to the IDM team, Identity and Access Management, to investigate what is wrong with their access process.

A specific example of using OneLogin Customer Identity to resolve an access problem occurred when a customer of mine was using an application and encountered access issues. We checked everything, such as his email and whether his SSO was configured correctly, and then reported the issue to the IDM team, which enabled access. The customer had only read access, so it was modified to provide him with modify access allowing him to use those applications effectively and complete his work on time.

While my main use case for OneLogin Customer Identity is quite positive, I can also say that the tool is really good, with continuous enhancements each year. Now, we are more frequently utilizing the AI tool, which will likely have a significant impact on the applications.

One of the best features OneLogin Customer Identity offers is that it is a third-party tool, and while the integration was initially tough to understand, we gradually learned how to integrate the applications our users and customers use in-house. Our customers are very happy with OneLogin Customer Identity, which allows them to access multiple applications without needing to register every time. After the initial registration, their user email ID is enabled, and this has made their work much smoother.

The integration process has saved considerable time for our team and customers because they only need to go to one portal to check their applications and log in from there. This efficiency allows them to work on other applications integrated with our in-house products, benefiting both customers and our in-house users and significantly reducing errors.

I want to add that the introduction of the AI tool opens opportunities for further enhancements, which we are actively working on as part of the product team. We aim to improve OneLogin Customer Identity to ensure it remains reliable and minimizes errors in the future.

The impact of OneLogin Customer Identity on our organization is positive because it reduces errors and decreases the workload. The automation of processes, especially concerning level one support that previously depended on service desk engineers, has been beneficial for our customers and users. Although there is a rare occurrence of issues that require following the P1, P2 process for resolution, the overall impact remains positive.

Previously, we dealt with multiple tools, including ServiceNow, that required manual logins across different browsers, creating many challenges. After implementing OneLogin Customer Identity, we launched all internal applications on OneLogin Customer Identity, allowing customers to log into just one application and access everything without hassle. This consolidation has created an automated system, leading to positive customer feedback about the significant impact on their workload.

OneLogin Customer Identity can improve by focusing on enhancements that promote reliability and independence from other applications. These improvements will better serve our customers and make the product even more dependable.

There are many potential enhancements, with one of the best being the implementation of passwordless authentication. Transitioning from traditional password authentication to biometric verification would greatly enhance security and user experience.

I have been using OneLogin Customer Identity for about four years.

OneLogin Customer Identity is stable.

At the moment, I have not faced any challenges with OneLogin Customer Identity's scalability. The difficulties experienced during integration were due to it being a new product for us, but now that I have hands-on experience, it has proven to be a reliable tool for our customers.

My experience with customer support for OneLogin Customer Identity has been positive.

My advice for others looking into using OneLogin Customer Identity is to be specific to the domain, understand the MFA setup, and know how to handle locked accounts and forgotten passwords, guiding users on how to connect with the IT department. We also aim to provide hands-on experiences that help users familiarize themselves with OneLogin Customer Identity's access process.

I would recommend OneLogin Customer Identity to large organizations because it is very effective at saving time for customers. It is crucial for customers to understand how the MFA works and be familiar with lockout policies and password reset procedures. OneLogin Customer Identity can provide a direct link for users to reset their passwords without intervention. Moreover, I suggest enabling passwordless authentication, especially for customers using personal devices.

The accuracy and reliability of OneLogin Customer Identity's output are sometimes problematic, but these issues are being addressed with collaboration between internal teams focused on security and product development.

Regarding OneLogin Customer Identity's AI capabilities, my thoughts focus on governance and security. When it comes to the security and governance of the AI features, I am aware that while AI has potential, it can also pose risks, especially when it involves breaking the code. Tools like Microsoft Copilot and ChatGPT show that there are challenges, indicating that the AI features still need significant improvements for data security.

I rate OneLogin Customer Identity an 8 out of 10 at the moment because it is functioning really well. I chose 8 out of 10 because I believe no tool can be 100% perfect; every product needs improvement and enhancement over time, which is why I deducted two points.

OneLogin Customer Identity has multiple use cases. I deployed this customer identity platform for about one and a half years with a customer whose primary use case was wanting a seamless customer experience that could provide customized branded registration and login experiences according to their wishes. We defined it according to their requirements. They also wanted feasible customer authentication and authorization that implements MFA options such as biometrics, passkeys, and SMS.

There can also be use cases for centralized identity management, which consolidates identities across multiple brands or applications into a single directory for better management and insights. In this case, the customer had three different environments and wanted central management. For that, we used OneLogin Customer Identity. They also wanted better and secure migration of legacy users. They had very old user data, so we used the migration hook, which is the best feature in OneLogin. It allows users to log in with their old credentials which are validated against an external database, and it is easily migrated seamlessly to OneLogin during the login process.

OneLogin Customer Identity has a feature of passwordless authentication. For social registration to speed up the user experience, we used passwordless authentication. They have that feature in their user and settings folder.

OneLogin Customer Identity has some core categories. If a customer wants to use APIs related to authentication, we build a custom login page, then manage multi-factor authentication, then establish a secure user session. It depends on the client's needs. We have used a couple of APIs there. Then it comes to their administration APIs, which allow you to programmatically develop user management, which creates, updates, and deletes customer records. It has enough support of APIs.

There are some issues I dislike about OneLogin Customer Identity. Customers are still facing performance inconsistencies. Many times users have reported issues such as slow loading times, some occasional browser extension failures, and long session timeout behaviors.

There is also complex implementation and configuration. Setting up this product can be demanding, particularly for an organization with a complex application, legacy applications, or larger application data which requires extensive custom workflows or a need for advanced branding. This will take a larger amount of time for deployment. Customization is easy but it takes time to customize, so it depends on the situation.

Occasional service interruptions also occur. During my tenure, some users reported occasional outages or connectivity glitches which disrupted access to business applications.

I have used it for almost one and a half years, starting from 2024 to mid-2025.

In terms of scalability for OneLogin Customer Identity, I don't think it has great scalability because many times users have reported issues about their loading browser extension and sometimes their session timeout. That was a disturbing performance. I don't recommend it for a client if they have a larger user base. If they are a very small-scale organization, then they should prefer OneLogin Customer Identity.

OneLogin Customer Identity has region-wise technical support. If we work in Asia, they have dedicated support people. If you are working from the USA, then they have a dedicated support system from the USA. They have a dedicated support system and availability depends on the package purchased. If a customer has purchased a P1 level package, then they are available immediately. If the customer has purchased a P2, then they are available in two hours. If customers purchase a P3 level product, then they are available in 24 hours. The time varies depending on the price they have purchased.

I have used Okta CIAM and Ping Identity CIAM.

Deployment of OneLogin Customer Identity is moderate. It depends on the client's requirement. Some clients want three applications and one AD base, which took almost 20 to 25 days for complete deployment. Some clients have larger application integration, which took almost six months for step-by-step integration. It takes time depending on the client's requirement and the number of applications to be deployed.

I was a developer as well as support and admin. I had a team of 10 people. Out of that, we were six developers and four were support and admin. We collectively worked on it.

I'm not sure of the exact rate, but OneLogin Customer Identity is cheaper than Okta. Okta is costly, and OneLogin is cheaper. It depends on the client and their budget. If they don't have a large budget, then they can prefer OneLogin Customer Identity, and if they have enough budget, then they should go for Okta.

I prefer Okta more than OneLogin. People should choose Okta if they want advanced customization and extensive third-party integration. Okta has around 7,000 pre-built applications. They have very extensive third-party integration and a very large user base. They are very good in support as well as documentation. People should choose Okta over OneLogin. For OneLogin, if a customer is looking for a cost-effective solution with faster setup and excellent simple-to-use workflows, then they should go for OneLogin.

Speed is moderate and quality is good. For support, I would rate it as eight out of 10, and for quality, it is a full 10 out of 10 because I haven't faced any issues and they have supported us a lot of times. Overall, I would rate OneLogin Customer Identity as seven out of 10.

I have been dealing with OneLogin Customer Identity for around one and a half years. The major use case for identity management includes a multifactor authentication module and identity management for both internal and external CIAM (Customer Identity Management). Since it deals with financial and banking, it is crucial to identify the customer accessing core banking and mobile banking, as well as managing internal identities such as privileged access management and employee-to-employee management.

The biggest benefit of OneLogin Customer Identity for cybersecurity in a banking environment is the ability to manage many virtual machines, servers, and applications that require different credentials and privileges by using single sign-on, which automates the process. It can be challenging to remember every application's password, so managing access centrally with single sign-on and multifactor authentication is recommended for both financial institution customers and internal employees.

Furthermore, identity access management encompasses more than just credentials and privileges; it includes user identity, behavior, and characteristics, driven by machine learning, and is increasingly required in my country, Ethiopia.

Passwordless login may improve user satisfaction and security in general by functioning in a manner similar to single sign-on, as it allows users to log in using their email account to access LinkedIn and other social media in a similar fashion.

Analytics is valuable in OneLogin to optimize customer identity strategy by characterizing user behavior and characteristics for security posture. It helps identify unusual activities or deviations from normal behavior, enabling actions such as blocking access or sending notifications. Each user has unique characteristics, making identity management encompass more than just a password and username.

I see areas for improvement with OneLogin as most clients require a market reference or evaluator report, such as a Gartner report, to be convinced to use a new product. Many vendors lack clear documentation or site references. Clarity in documentation, similar to that with Thales and Fortinet, simplifies our job and helps us convince clients by providing links to credible sources.

There may be latency issues with OneLogin Customer Identity, as most of these security products are virtual and software-based. Latency and performance depend on the physical server, and fulfilling vendor-recommended resource requirements will ensure functionality; thus, if those requirements are met, there should be no issues.

I have been in the domain of identity management for more than one and a half years, with a strong focus on cybersecurity products, not limited to OneLogin Customer Identity.

I see no limitations regarding scalability with OneLogin Customer Identity.

I am not certain about ROI related to OneLogin Customer Identity, but it is vital to protect financial institutions' resources and core banking, which I consider a significant ROI. Protecting these assets is crucial, especially for financial institutions, to mitigate risks.

Compared with CyberArk, I would say OneLogin Customer Identity is affordable. Comparing OneLogin Customer Identity with CyberArk technically, I think CyberArk is better; I have had CyberArk for around two years or more, and I know of two or three customers in Ethiopian financial institutions using CyberArk Identity Access Management. According to Gartner, CyberArk is superior, but we are also competitive with OneLogin Customer Identity.

I have worked in presales and deployment in my country, Ethiopia, specifically with load balancers. I have been involved in presales and deployment with the F5 load balancer and Radware load balancer.

For the F5 load balancer in presales, I have been involved with LTM (Local Traffic Manager) and ASM (Advanced Application Firewall) for the WAF in a single appliance, which integrates WAF and load balancer in a single appliance. In deployment after-sales, I have worked with the basic load balancer only, specifically not for the WAF; however, in terms of WAF deployment, I have experience in FortiWAF deployment, presales, and deployment, while for load balancer, I have worked with Radware ADC load balancer and F5 LTM.

I do work with F5 Silverline Managed Services for firewall and Web Application Firewall. I do not work with F5 Distributed Cloud Services, as most of our customers' current need is on-premises products and solutions.

I do not work with NGINX products such as NGINX App Protect or NGINX Ingress Controller. I have experience with LTM, WAF, and BIG-IQ, the central manager.

For other products regarding identity management, I have been involved with CyberArk in presales only. For CyberArk, I work only with Identity Access Management. I do not work with CyberArk IGA powered by Zilla, as CyberArk's offerings are on-premises.

For Fortinet products, I am involved with Fortinet WAF, specifically on-premises and the physical appliance. For Fortinet AppSec, the application monitoring is a cloud-based software as a service, and as I highlighted earlier, most of my clients, such as financial institutions and banks, need on-premises solutions; thus, for the majority of the vendors, I have been involved in the on-premises solutions.

For API capability, I think this is common and a must for the majority of the vendors, as API is essential for integration; for instance, in identity management, integrating with SIEM to centralize logs is crucial for security management, allowing security operators to analyze logs for attacks or activities. API integration with third-party applications is vital; the customer typically handles third-party API sections, while we manage our product integration using vendor support procedures.

For the centralized management console, I note that in terms of deployment, if the IAM application, specifically OneLogin Customer Identity, is deployed in a main data center, DR, and various servers as high availability in a multi-deployment architecture, central management is indispensable. It allows management of configurations and operations centrally from one machine instead of logging into multiple instances.

Regarding OneLogin Customer Identity, for deployment options and license comparisons with other vendors, I am involved in the presales; if we win an opportunity, we will deploy together with vendors. After deployment, I will assess the ease of deployment, such as for Fortinet products where I have been involved with SIEM, next-generation firewall, and WAF along with F5 and Radware load balancers. For OneLogin Customer Identity specifically, it is still in progress, and I will provide updates once I am involved in the deployment.

My overall review rating for OneLogin Customer Identity is 8 out of 10.