OneLogin Customer Identity

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.