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.

My main use case for OneLogin Customer Identity is that it is a very easy-to-use platform with a great design, making it accessible for everyone in my organization. Every employee in our company uses OneLogin because it helps us securely store our credentials. Strong, long passwords are a must for security nowadays, but it is almost impossible for humans to remember them, and storing them in notes is a security breach by itself. When OneLogin encrypts all the sensitive data before saving it, it also gives us easy access whenever we need to log into our apps.

A specific example of how my team uses OneLogin Customer Identity in our daily workflow is when we are working remotely and we want to collaborate on a certain project. We use different apps that are integrated into OneLogin, so we have access despite working remotely. We can access it at any time because we use one strong password, which is very easy to manage, and it is easy to access our apps easily, thus enhancing our collaboration while keeping away unauthorized users.

OneLogin Customer Identity helps us manage our different accounts, and it also assists with our single sign-on.

Some of the best features that OneLogin Customer Identity offers are its ease of use for almost all our users in my organization, connection to Active Directory, and secure login for all our applications.

The connection to Active Directory helps my team by allowing us to use applications such as Asana and monday.com, and whenever we are working on a certain project, it helps us log in to those apps without using any password, making it very easy to access all our documents in one place and save time.

I would also note that the user interface of OneLogin Customer Identity is very customizable and easy to navigate, being very user-friendly. It saves a lot of time by remembering the credentials and logging in once. Additionally, it ensures security for all our applications and privacy on HIPAA and PCI compliance platforms, making it easy to store our employee passwords so that our tech team does not spend a lot of time restoring those passwords or troubleshooting.

OneLogin Customer Identity has positively impacted my organization by greatly improving security. We have reduced the time spent on forgotten passwords for both employees and my tech team, which has had a positive impact on time management.

In terms of specific numbers, before we had a very poor pool of security breaches and it was not easy to log into every application in my organization, as we manually logged into every application. However, when we got OneLogin, it really simplified how we log in by using just one password or going passwordless, and we have been able to save at least 70 to 80% of our time compared to our previous tool.

I think OneLogin Customer Identity should be improved by ensuring users receive notifications when their passwords are about to expire.

Additionally, I noticed that training is a must. A training and learning curve is necessary for everyone to go through, and I would love the option to skip the training if the user already knows about the system. This would be time-saving for everyone.

I have been using OneLogin Customer Identity for the past five years.

OneLogin Customer Identity is absolutely very stable.

Its scalability is great because it can handle my organization's growth, so it is very scalable.

The customer support for OneLogin Customer Identity is okay; they are very responsive, on time, and quick to find solutions to all our issues.

We previously switched from Skype for Business.

The setup was quite straightforward, easy, and had no technical glitches.

We have seen a good return on investment because OneLogin Customer Identity saves employees time by giving us one password to log into all our apps, making our projects more secure and being cost-effective compared to other alternatives.

Regarding pricing, setup cost, and licensing, I find the price to be very affordable, and we have seen improvements in security and advantages in using this platform.

Before choosing OneLogin Customer Identity, we evaluated other options, specifically Microsoft 365 Business Premium.

My advice for others looking into using OneLogin Customer Identity is that if you want to improve the security of all your applications, save time while having a single sign-on and passwordless experience, you should definitely use OneLogin because it is also very cost-effective and easy to use for everyone. I would rate this product a 9 out of 10.