I do use OneLogin to get into the Ivanti application. Our usual use case for OneLogin is to use it as an SSO to access the Ivanti VPN, which we use to access particular sites and applications in our work platform.

What I appreciate most about OneLogin is definitely SSO, which avoids us having to enter the password, saving time. Since I work in the technical support department, it saves our time in what would otherwise be a time-consuming process where we would avoid entering credentials repeatedly whenever we connect to the required VPN and the tools.

OneLogin provides a good end-user experience for signing in and authenticating to needed applications, which involves time-consuming efforts when users or employees are completely occupied with different tasks. Since we work in IT, we might have multiple passwords to get into different tools. However, when it comes to OneLogin, we avoid this complexity; we just have to remember one tab, and when we note down our user account, it directly asks for OneLogin with multifactor authentication, where we just have to authenticate it to get in successfully.

OneLogin is going well currently. As for optimizations in OneLogin, it would be useful to have an option on OneLogin site to remember the user ID. Currently, we do not have that option, and every time we log in, we have to enter our OneLogin username and then get it authenticated. If a 'Remember Me' option were available, we could directly proceed with the authentication instead of having to enter our username every time. This is the one point we have identified.

I have been using OneLogin for the past two years.

OneLogin is stable. I have been using it for the past two to three years and have not faced any issues with it. It is very stable. For some tools, there are notifications or expiry alerts for the concerned tool or MFA factors, but here we do not have anything as such.

We had outages, but in our team, we have a different department for escalation, so we escalated to the concerned OneLogin support team, and they fixed that issue.

I find OneLogin to be mid-level scalable because I use only the first level of access, so we have not checked the in-depth functionality. I am happy with the level of scalability that OneLogin provides.

My thoughts on the technical support and customer service of OneLogin are that it plays a major role for us to assist users. We use it for the connection of VPN, which allows us to get into remote sessions with users, and it is essential for us to take remote sessions with users and assist them in resolving their issues in a timely manner.

I do not often communicate with the technical support specialists of OneLogin. We just have a mail ID, so if we face any issue, we can send them an email for assistance. Till now, I have not faced any issues with OneLogin; it is running smoothly.

From the beginning, we started using OneLogin. First, we were using Microsoft credentials to get into the tools, and later it upgraded to OneLogin.

I found the initial setup of OneLogin to be very easy because it is just about downloading the application and setting it up through scanning the URL on OneLogin portal. The process was very simple, and there was no complex issue I faced during the setup process.

We have a KB article provided by my team, which we use to set it up or configure the applications, reset, etc. I have found the documentation sufficient; all necessary details were very simple and clearly mentioned by our SMEs, so we have not faced any issues with the given articles.

I have evaluated other solutions, such as Delivery, which works similar to OneLogin. Delivery DID account exactly works as OneLogin, but it inserts different account profile accounts.

We use OneLogin Okta as an MFA for OneLogin process to adjust authentication flows in real time, depending on the risk score associated with the login attempt.

We do not use the SmartFactor Authentication of OneLogin, as even Okta is an authentication process; it is a multifactor authenticator.

I use Okta and OneLogin simultaneously.

I was not part of the decision-making process.

I am aware of setting up OneLogin for Symantec and Okta setup on the mobile applications, including the basic configuration.

I am not aware of the pricing and licensing of OneLogin.

I have not worked on the user identity synchronization across directories functionality of OneLogin yet.

The integration of phishing-resistant device trust impacts our authentication processes positively because we have a team that verifies everything, and they guide us to configure it. All the configuration and security information is checked by our security team, and based on their updates, we proceed.

Integrating the single sign-on feature with third-party authentication providers is very easy; I have not faced any difficulties. When we try to connect with third parties, I have assisted users in setting up OneLogin accounts for access to particular third-party tools, and there are not many difficulties. We just have to understand the process.

When you understand the product usage, you will not face any issues with it.

I have not used the adaptive login flows with Vigilance AI.

I do not have any insights regarding the role of HR-driven identity management in streamlining employee identity handling in my organization.

In MFA, at the desktop support or customer support level, MFA plays a major role that includes security, compliance, and also a two-way authentication process.

MFA is important for us because it ensures our data is safe, avoiding security issues related to our accounts. If any unauthorized attempt occurs, we receive notifications on our mobile devices, ensuring that it is not possible for others to access our account without our consent. This is a significant advantage of OneLogin or MFA.

In OneLogin, customer identity and access management for external clients is not something I go in-depth with; I assist users only in configuring OneLogin and setting up MFAs. We have two MFAs in OneLogin: Symantec and Okta. My role is to help users set up either of the MFAs to ensure they can access their client VPNs based on requirements successfully without issues.

I rate this review a 9 out of 10.

OneLogin serves as our centralized identity and access management platform. We previously used it as single sign-on, so users could access multiple business applications with one set of credentials instead of managing separate logins for everything. We also use it for user provisioning and de-provisioning to make onboarding and offboarding more efficient. One practical benefit is reducing password-related issues and giving users a smoother experience. At the same time, one challenge we notice is that integration can vary depending on the application. Standard cloud applications are usually straightforward, but some legacy or custom applications need additional configuration and testing. So it is not always a completely plug-and-play process.

Beyond SSO and access management, OneLogin also helps from a user experience and security perspective. Having a single place of authentication reduces password fatigue for users and cuts down on password reset requests, which can take up a lot of IT support time. At the same time, identity management is rarely a one-time setup. As organizations grow, applications change, and access requirements evolve. One challenge is maintaining the role structure and ensuring users continue to have the right level of access over time. Even with OneLogin, periodic access reviews and cleanup are still important because automation can help with efficiency, but governance still needs ongoing attention.

Single sign-on is the most valuable feature I find in OneLogin. From a user perspective, it makes daily work easier because employees do not have to remember different credentials for multiple applications. It improves productivity, but it also reduces password reset requests from the IT team, which can become a frequent support issue.

Another useful feature is automated provisioning and de-provisioning. Once users are linked to a role or group, application access could be assigned more effectively, and access removal becomes more controlled during offboarding. I would also mention MFA, multiple factor authentication, and adaptive authentication. Having an additional authentication step for higher-risk logins adds an extra security layer without applying the same restriction everywhere.

One practical advantage is the large application integration catalog because it simplifies connecting common enterprise applications. At the same time, in a real environment, there are still gaps that no identity platform fully solves. Modern cloud applications usually integrate smoothly, but some legacy systems or applications without proper federation support can still require manual processes. I have had situations where offboarding for non-integrated systems needed separate tracking, which can create security and audit concerns if not monitored properly.

OneLogin works well for centralized identity and access management, but there are a few areas where I think improvements could help, especially in larger or more complex environments. One area is integration with legacy or highly customized applications. Modern cloud applications are usually easier to connect, but older systems can still require additional configuration or workarounds. Having more flexibility and simpler integration options for those cases would help. I think reporting and visibility could also always improve. Organizations often want more detailed insight around user activity, access patterns, and audit information without needing additional tools or custom work. Another area is simplifying administration for complex environments. As companies grow, role structures and access policies can become difficult to manage. Small changes can sometimes have a wider impact and clear visibility into access relationships and dependencies would be useful. I would also say this is not only OneLogin's challenge but an industry-wide one. Balancing security and user experience is crucial. Organizations want stronger authentication and tighter controls, but users also want fast and simple access. Finding that balance is still something many identity platforms continue to improve.

I have been using OneLogin for the last four years.

In my experience, I would describe OneLogin as generally stable for day-to-day operations. Most of the time, authentication, SSO, and user access processes work consistently, and users typically do not notice issues during normal usage. From an operational perspective, stability is especially important because identity platforms become a centralized dependency. If OneLogin has an issue, users can suddenly lose access to multiple applications at the same time. So reliability matters a lot.

In my experience, OneLogin handles scalability reasonably well and adapts well as the environment grows. As we add more users, applications, and access requirements, we do not see a major need to redesign OneLogin itself. The cloud-based model helps because scaling users and applications feels more like expanding configuration rather than adding infrastructure. OneLogin is designed for enterprise-scale identity management and has been used across large environments with sustainable authentication volumes.

My experience with customer support is generally okay, but I would describe it as a mixture rather than consistently exceptional. For standard questions or routine issues, responses are usually helpful and documentation covers many common scenarios. So not every issue requires opening a ticket. User review platforms generally rate OneLogin support positively overall, though experiences vary across customers. We do contact support occasionally for things like integration questions or troubleshooting authentication behavior. For straightforward issues, the experience is usually fine. More complex cases sometimes take longer because they need additional investigation or escalation.

Before moving to OneLogin, we were using a more traditional setup with a combination of directory services and some application-specific authentication methods, rather than a fully centralized identity platform. The main reason for moving was to simplify access management and improve the user experience. Managing authentication separately across multiple applications was becoming difficult as the environment grew. Users had multiple credentials to manage, onboarding required more manual work, and maintaining access consistency across systems became harder. OneLogin helped by bringing everything into a more centralized model with SSO and more automated identity processes. That reduced some operational overhead and gave better visibility into user access.

One thing I have noticed is that migrations themselves can also be challenging. Moving users or reconfiguring application integration and ensuring a smooth user transition takes planning. So even when a new solution is better long-term, there is still some effort involved during the change.

The setup itself is generally straightforward for standard integration. One thing I notice, though, is that regardless of the cloud provider, the bigger challenge is usually not connecting OneLogin itself. It is maintaining consistency, access policies, and integration as the environment grows. Once organizations start using many applications across different teams, access management can become more complex over time.

OneLogin is primarily deployed in a hybrid environment in our case. OneLogin itself is cloud-based, but we still have a mix of cloud applications along with some on-premises or legacy systems that need to be integrated. That setup works well because it allows us to use the benefit of OneLogin as a cloud identity platform while continuing to support existing systems that the organization could not immediately migrate. In reality, many companies are in a similar situation where everything is not fully cloud-native yet. One practical challenge with a hybrid setup is that it can add some complexity around integration, synchronization, and maintaining consistent access policies across different environments. Modern SaaS applications usually integrate more smoothly, while older systems may require additional configuration or ongoing maintenance.

We did see ROI, although I would describe it more in terms of operational efficiency and time saving rather than saying we reduce headcount. We do not suddenly need fewer employees. Instead, the IT team spends less time on repetitive tasks and more time on higher-priority work. If I had to give a rough estimate from what we observe, password and login-related support requests likely reduce around thirty to forty percent and onboarding provisioning activity becomes noticeably faster once automation and centralized access management are in place. OneLogin also reports that organizations commonly see significant reductions in help desk volume and provisioning effort.

From my perspective, I am not directly involved in the procurement or contract negotiation, so I have more visibility into usage and implementation than the exact pricing details. But my general impression is that OneLogin's pricing model is fairly standard for an identity and access management platform and is typically based on factors like the number of users and the selected features. For setup costs, it all depends on the environment's complexity rather than just the product itself. If an organization mainly has standard cloud applications, the setup feels more straightforward. On licensing, one thing I notice is that organizations sometimes need to plan beyond current requirements. Features such as advanced security capabilities, additional integrations, or future growth can affect overall costs over time. One practical challenge I have heard discussed across teams is that OneLogin's license cost is often only part of the overall investment. Time spent on implementation, administration, and maintaining integration can also become important factors when looking at the total cost of ownership.

We looked at a few other identity and access management options during the evaluation process, including Okta, Microsoft Entra ID, and solutions like Ping Identity. The comparison was not only about features because most mature IAM platforms cover core capabilities such as SSO, MFA, and user lifecycle management. The bigger discussion was around things such as integration effort, compatibility with other existing environments, ease of administration, user experience, and overall cost. OneLogin felt like a reasonable balance for our requirements at the time. It covered the functionality we needed without making the environment feel overly complex.

Single sign-on has the biggest impact for our team on a daily basis. It is one of those changes that people notice pretty quickly because employees no longer have to keep track of multiple usernames and passwords. Support tickets related to password resets and login issues also become less frequent. So the IT team spends less time on repetitive tasks and can focus on other work. For MFA and adaptive authentication, the experience is generally straightforward for users. The idea is not to challenge users for every single login. For example, if someone logs in from their usual device or normal location, the process feels almost seamless. But if there is a login attempt from a new device, unusual location, or something that looks higher risk, additional verification could be triggered. Initially, there is some adjustment because users sometimes see the extra authentication step as inconvenient. We had a few questions around things such as changing phones, registering devices, or getting prompted unexpectedly. But once people understand that it is mainly for protecting accounts rather than adding extra work, adoption improves.

One thing I would add about features generally is that technology itself is usually only part of the solution. Features can work really well, but user awareness and process consistency still matter. A common challenge in many organizations is balancing security and user convenience. If controls become too strict, users get frustrated. If they are too relaxed, security risks increase. Finding that balance is still something many teams continue to work on.

The reduction in password reset and login-related tickets was probably somewhere around thirty to forty percent over time. It was not an overnight change because users still need time to adapt, but once SSO becomes part of daily usage, the support load definitely becomes lighter. In terms of time-saving, onboarding that previously could take several hours, especially when multiple applications and approvals were involved, becomes much faster. A good portion of the access setup could be completed automatically based on roles or groups. So in many cases, users could get access the same day without as much back and forth between teams. From a security and compliance perspective, centralized access management also improves visibility. During audits, it becomes easier to review who had access to what because information was more consolidated instead of spread across different systems. We also reduce the chances of inactive accounts being missed during offboarding. I would not say OneLogin completely eliminates security incidents because many risks still come from phishing, weak user practices, or unmanaged applications outside OneLogin. But having MFA and stronger access control definitely reduces some common risks related to compromised passwords. One ongoing industry challenge is that the identity environment can become complex as organizations grow. Over time, role structures, exceptions, and temporary access requests can pile up. So governance still requires continued cleanup and review. The tool helps a lot, but maintaining long-term access hygiene is still something many companies struggle to get on top of.

As environments become larger, managing access can become more complex than expected. The initial setup may be straightforward, but over time, organizations add more applications, users, and exceptions, and maintaining everything can require ongoing effort. Another point that sometimes comes up is troubleshooting. When authentication issues happen, especially across multiple integrated applications, teams may want faster root cause visibility. Sometimes the issue is not with OneLogin itself. It could be an application configuration, directory sync issue, or policy setting, but identifying exactly where the problem is still takes time. I have also heard discussions around making automation smarter. For example, many organizations still rely on role-based rules, but in real environments, user responsibilities change frequently. There is still a broader industry challenge around dynamically adjusting access based on changing roles, projects, or user behavior without creating unnecessary complexity.

We primarily use Azure alongside OneLogin. It fits well with the environment because a lot of our applications and user management processes are already connected to the Microsoft ecosystem. OneLogin works as a centralized identity layer while integrating with different applications and services.

HR-driven identity management plays an important role because it helps connect employee lifecycle events with access management processes. Instead of IT manually tracking every employee change, information from the HR system acts as a source for identity-related actions. For example, when a new employee joins, HR data such as department, role, or job title helps trigger account creation and assign initial access automatically. Similarly, when someone changes roles internally, access can be updated based on the new position, and when an employee leaves the organization, offboarding actions can start more quickly. The biggest benefit is reducing manual effort and improving consistency. It also helps avoid situations where access requests are delayed or someone retains access longer than needed. I would say HR-driven identity management helps streamline employee handling significantly, but good data quality and coordination between HR and IT remain important for it to work effectively.

The impact of phishing-resistant device trust is mainly around strengthening security without creating a completely different login experience for users. Phishing-resistant device trust adds another layer of confidence by considering not only who the user is, but also whether the device itself is trusted and meets security requirements. From an authentication perspective, it helps make decisions more context-aware. For example, if a login comes from a recognized and compliant device, the process remains smoother. If the device is unknown or does not meet certain conditions, additional verification or restrictions could be applied.

I would rate OneLogin around eight out of ten overall. The reason I would not give it a perfect score is that it does a good job with core areas such as SSO, MFA, centralized access management, and improving user experience. It can save time and simplify identity-related tasks in day-to-day operations. I give it an eight because it performs well in the areas it is mainly designed for. It improves access management, simplifies authentication with SSO, and helps reduce manual effort for onboarding and offboarding. For day-to-day use, it provides real value and generates a better experience for both users and the IT team. The reason I did not rate it higher is not because of a major issue, but because there are still areas that can become challenging in real environments. As organizations grow, managing complex role structures, handling exceptions, and integrating older or custom applications can take more effort than expected. For OneLogin to move closer to a ten for me, I would like to see even stronger automation and easier management for complex environments. Better troubleshooting visibility would also help, where administrators can quickly identify whether an issue comes from policy, integration, synchronization, or the application itself.

OneLogin's main use case is in a company where employees use multiple applications like Microsoft 365, Salesforce, VPN, and HRMS. Without OneLogin, employees would need a separate username and password for every application. By implementing OneLogin, the organization can enable SSO, which is Single Sign-On. Employees log in once and securely access all the authorized applications from one dashboard.

For example, if an employee leaves the company, the IT team can disable the OneLogin account once, and access to all the connected applications is automatically revoked. This improves security, saves administrative time, and also reduces the chances of unauthorized access. Overall, OneLogin improves productivity, strengthens security, and simplifies user management.

For the main use case, another important aspect is MFA, which adds an extra security layer.

OneLogin has positively impacted us by saving time, and it also reduces administration work.

The biggest impact was the reduction in password-related issues because employees could access multiple applications using SSO. This reduced helpdesk tickets and also saved IT time. Apart from this, the organization benefited through better security, less administrative effort, and reduced downtime for users. There is also a better user experience.

Time has been saved significantly. It is quite beneficial because it helps the organization save both time and cost.

The best features OneLogin offers are SSO, basically Single Sign-On, where a user can access multiple applications with one login. As I mentioned, MFA is there, which adds an extra security layer. Then, there is directory integration, which works well with Active Directory and also LDAP. Apart from this, there is a centralized access control dashboard that is easy for administration to manage users and permissions.

For centralized day-to-day tasks, we can basically use it for monitoring purposes. It is easy for administration. We can see and monitor users as needed. Whatever permissions we have to give, for example, if an organization has applications like Outlook, VPN, Salesforce, or any other cloud services, the administrator does not need to log into each application individually to manage users. Everything can be controlled from the OneLogin dashboard. I can add or remove users, reset passwords, and give or revoke application access anytime I want. Apart from this, I can monitor login activities.

In terms of improvement, there is not much to improve, but the biggest improvement was the reduction of password-related issues because employees could access multiple applications. Overall, the organization's experience is good regarding the improved security and reduced administrative effort. Better productivity is evident. OneLogin is a strong IAM solution with minimal areas for improvement.

I have been using OneLogin for the last 1.5 years.

OneLogin is scalable, which is good and better for the future.

Customer support is excellent. It supports us every time, 24/7.

I would recommend OneLogin because it is user-friendly, secure, and scalable. It simplifies identity management for IT teams while giving users a smooth login experience. OneLogin is very effective in improving both security and operational efficiency.

I have already mentioned that it provides better security. It is also reliable and very useful for an organization managing multiple applications and users. My review rating for OneLogin is 9 out of 10.

My main use case for OneLogin is managing secure user authentication and single sign-on across multiple business applications and for user provisioning, user control, and multi-factor authentication.

A specific example of how I use OneLogin for those purposes in my day-to-day work includes identity and access management, especially for single sign-on and secure user authentication across multiple applications and services.

I do use the solution's Smart Factor Authentication to adjust authentication flows in real-time depending on the risk score associated with the login attempt, and I assess it as very effective from a security perspective because high-risk or unusual login attempts trigger stronger authentication controls. The balance between security and usability is one of the strongest points of Smart Factor Authentication because it improves protection while minimizing friction for the end user in day-to-day operations.

My impression of the user identity synchronization features in OneLogin is very positive; it works well for synchronizing users across different directories such as Active Directory, LDAP, cloud directories, and HR systems.

The integration of phishing-resistant device trust impacts my authentication processes by reducing the risks of phishing-based attacks, credential theft, and unauthorized access because authentication decisions are based not only on passwords but also on device trust and user behavior.

I have not used the adaptive login flows with Vigilance AI.

When employees change departments or leave the organization, access permissions and accounts are automatically updated or revoked, although I do not use HR-driven identity management.

I would like to add that the multi-factor authentication features in OneLogin help improve account security by adding an extra layer of protection beyond just passwords.

The best features OneLogin offers, in my opinion, include centralized identity and access management, a simple and user-friendly dashboard, secure remote access for users working from different locations, and good reporting and monitoring features for security and compliance.

Out of those features, I find myself relying on multi-factor authentication the most because it helps improve account security by adding an extra layer of protection beyond just passwords, and the centralized dashboard and automation features also help reduce manual work related to user provisioning, password management, and access review.

OneLogin has positively impacted my organization by allowing users to securely access multiple applications with a single sign-on, improving user experience, and reducing password-related issues and support tickets.

From a security perspective, features such as MFA and authentication help reduce the risks of unauthorized access and improve visibility into suspicious login activities, which contributes to measurable drops in password-related support tickets and time saved for our IT team after implementing OneLogin.

I believe support response time and troubleshooting for complex integrations could be improved in some cases for OneLogin.

I have noticed that customization of reports and alerts would make daily operations even smoother for security and IT teams.

I have been using OneLogin for the last one year.

OneLogin is stable.

OneLogin's scalability is quite stable and works well for growing organizations and enterprise environments; in our case, it handles an increasing number of user applications and authentication requests effectively.

Customer support is good.

Before implementing OneLogin, we were mainly using traditional Active Directory-based authentication, and we switched to OneLogin to get centralized identity and access management, single sign-on, and multi-factor authentication.

My experience with pricing, setup cost, and licensing for OneLogin has been generally positive. The initial setup required proper planning, especially for integrating Active Directory, and we also saw value from reduced password-related support tickets.

OneLogin was implemented through the organization's standards licensing and procurement process, and not purchased through the Azure Marketplace.

We have seen a good return on investment after implementing OneLogin, with the biggest improvements being reduced support efforts, faster user management, and stronger security controls.

My experience with pricing, setup cost, and licensing for OneLogin has been generally positive.

We evaluated a few other IAM and SSO solutions such as Okta and Microsoft Entra ID before choosing OneLogin.

I would advise organizations considering OneLogin to first understand their application environment, user access requirements, and user provisioning needs, as this helps make the implementation smoother and more effective. I would rate this review as a 9.

OneLogin serves as our main identity and access management solution, particularly for centralized authentication, single sign-on, and secure access management across enterprise applications and systems.

One practical example of how we use OneLogin for centralized authentication and secure access management in our organization is for centralized access to multiple enterprise and cloud-based applications through single sign-on. Instead of maintaining separate credentials for different platforms, OneLogin allows authentication through a single, centralized identity system. When employees log in to the organization environment, they can securely access authorized applications using a single authentication process combined with multi-factor authentication. This simplifies the login experience for users while improving security by enforcing centralized access policy and strong authentication control.

We also use OneLogin for role-based access management and user provisioning. When a user joins the organization or changes roles, access permissions can be managed centrally, helping ensure users only receive operational access based on business requirements.

OneLogin is primarily deployed as a cloud-based identity and access management solution within our organization.

OneLogin's best features include its single sign-on, MFA, multi-factor authentication, and centralized approach, which improve operational efficiency, reduce password-related support issues, strengthen authentication security, and provide better visibility into user access activity across the environment.

Single sign-on, combined with centralized access management, stands out as the most valuable feature for me. The biggest advantage is that it simplifies authentication for users while still maintaining strong security control. Instead of managing multiple usernames and passwords across different applications, users can securely access authorized systems through a single centralized authentication process. This significantly improves the user experience and reduces password-related support requests and administrative overhead.

Another feature worth highlighting is the platform's strong integration capability with cloud applications, enterprise systems, and identity providers. This makes it easier to centralize authentication and access management across different environments without requiring complex manual administration. The user provisioning and de-provisioning capabilities are also very valuable because they help automate access management processes and reduce the risk of outdated and unnecessary access remaining active within the environment.

OneLogin has positively impacted our organization by improving authentication security, simplifying access management, and enhancing the overall user experience for accessing enterprise applications and systems. The platform also strengthens security through centralized authentication policy and multi-factor authentication, helping improve access control and reduce risks related to weak and compromised credentials.

OneLogin is a strong identity and access management platform, but there are a few areas where improvement could enhance the overall experience and functionality. One area that could be improved is the user interface and administrative dashboard experience. While the platform is generally manageable, some advanced configuration and policy management tasks can feel complex, especially for organizations managing large environments with multiple integrations. Another area of improvement is integration flexibility and support for certain third-party and legacy applications where additional customization or configuration may sometimes be required.

I have been using OneLogin for more than two years.

OneLogin is stable.

OneLogin's scalability has been especially effective for organizations managing growing cloud environments, multiple enterprise applications, and an increasing number of users. The platform handles centralized authentication, single sign-on, multi-factor authentication, and user provisioning effectively as the environment expands. As more applications and users are added, OneLogin helps maintain consistent access management and authentication policies without significantly increasing administrative complexity. The platform's integration capability with cloud applications, directories, and enterprise systems also supports scalability by simplifying identity synchronization and access governance across multiple environments.

The customer support is positive.

We did not use any solution before using OneLogin.

My experience with OneLogin pricing, setup cost, and licensing is generally positive, especially considering the value it provides in centralized identity, access management, single sign-on, and multi-factor authentication. The initial setup and licensing costs are very reasonable for an enterprise identity platform. The total cost can vary depending on the number of users, authentication features, integration, and advanced security capabilities being used.

We have seen a positive return on investment from using OneLogin, primarily through reduced administrative workload, improved authentication efficiency, and time savings for both users and the IT team. We also experience operational efficiency improvements through centralized authentication and automated user provisioning and de-provisioning processes. Another important benefit was strong authentication security through MFA and adaptive authentication policies, which improve visibility into login activity and reduce risks associated with weak or compromised credentials.

Before choosing OneLogin, we did not evaluate other options.

I recommend that organizations first clarify and evaluate their authentication and access requirements before implementation. OneLogin provides the most value in environments where organizations need centralized authentication, MFA, SSO, and simplified access management across multiple cloud and enterprise applications. I recommend starting with a well-defined access management strategy and identifying which applications, directories, and user groups will be integrated into the platform.

Smart Factor Authentication provides a good balance between security and usability, especially in environments where organizations want strong authentication control without creating unnecessary friction for users. This makes it effective in its adapting and risk-based authentication approach. For example, if a user logs in from a trusted device and normal location, the authentication process remains smooth and user-friendly. However, if the login attempt appears unusual, such as from an unfamiliar device, unusual location, or suspicious network behavior, the platform can automatically trigger strong MFA requirements or additional verification steps.

My impression of the user identity synchronization functionality in OneLogin is very positive, especially for organizations managing users across multiple directories, cloud applications, and enterprise systems. The synchronization capability helps maintain centralized identity consistency by automatically managing user account information, access permissions, and authentication data across connected systems. This significantly reduces manual administrative effort and minimizes the risk of inconsistent or outdated user information across environments.

The integration of phishing-resistant device trust has had a positive impact on our authentication process by strengthening access security while improving confidence in user and device verification. One of the biggest benefits is the reduction of risk associated with credential theft, phishing attacks, and unauthorized device access. This support adds an additional layer of security to the authentication workflow because even if credentials are compromised, access from a trusted and managed device can still be restricted or challenged with strong authentication requirements.

OneLogin's ability to provide a seamless end-user experience for signing in and authenticating to needed applications is very positive. The platform does a good job of simplifying access to enterprise applications while maintaining strong security controls in the background. Single sign-on capability is one of the biggest strengths because it allows users to access multiple authenticated applications through a single authentication process without needing to repeatedly enter credentials for each system.

We have evaluated and utilized adaptive authentication capabilities similar to Vigilance AI, risk-based authentication, and strong access security within the environment. For example, when a user authenticates from a trusted device, it is effective. However, if we log in suspiciously, such as from an unknown device or abnormal access pattern, additional authentication factors or strong verification requirements can be triggered automatically. The adaptive login flow functionality has been valuable for identifying potentially risky authentication behavior based on contextual factors such as device information, login location, IP reputation, unusual access patterns, and user behavior.

I would rate this review a 9 out of 10.

I use OneLogin to give employees one secure login for applications like Microsoft 365, Atlassian, and internal SaaS tools, while enforcing MFA policies based on user roles and access location.

I use OneLogin as a cloud-based IAM platform integrated with both on-premises and cloud applications in a hybrid environment.

The best features for me are the single sign-on experience and its ability to offer centralized access management for a large number of pre-integrated SaaS applications. SmartFactor adaptive authentication feature is especially useful because it adjusts security requirements based on logic, risk, and user behavior.

SmartFactor has worked well because it adds extra verification only when login behavior looks risky. Users are not constantly dealing with MFA prompts during normal day-to-day access.

The integration library is definitely one of the strongest parts of the platform.

OneLogin has improved user access management, simplified the login experience for employees, and strengthened MFA enforcement across cloud applications without adding too much administrative overhead.

Onboarding and application access provisioning are much faster now, and I have also reduced password-related support tickets because users can access most applications through a single login portal.

Identity synchronization works well overall and helps keep user accounts, groups, and access permissions consistent across connected directories and cloud applications with minimal manual effort.

The adaptive login feature with Vigilance AI has been useful for identifying unusual login patterns and automatically applying stronger authentication when the risk level increases.

Enforcing MFA at the desktop level has strengthened endpoint security significantly because users still need strong authentication even when devices are offline. This helps reduce the risk of unauthorized local access.

The reporting and the dashboard customization could be more flexible, and troubleshooting federation or integration issues can sometimes take more effort than expected.

The UI is very easy to use, but some admin sections feel a bit outdated, and more detailed troubleshooting documentation would help during complex integrations.

There is still room for improvement in reporting, advanced customization, and some administrative workflows.

I would rate the customer support a nine on a scale of one to ten.

My use case for OneLogin is centralized identity and access management, particularly for secure single sign-on and user authentication across enterprise applications.

In my experience, some of the best features OneLogin offers are Single Sign-On, SSO, Multi-Factor Authentication that is MFA, centralized identity management, and automated user provisioning.

The feature that stands out the most for us is Single Sign-On, SSO. It has made a significant difference by simplifying access management for employees who use multiple enterprise applications daily. Before implementing SSO, users had to manage separate credentials for different systems, which often resulted in password-related issues, login delays, and increased support requests.

One feature that became more valuable over time was the automated user provisioning and de-provisioning capability. Initially, I focused mainly on SSO for authentication improvements, but later I realized how automated lifecycle management could improve operational efficiency and security. It helps streamline onboarding based on user role and position changes.

OneLogin has positively impacted our organization by improving security, productivity, and access management efficiency. Employees can securely access multiple enterprise applications with a single authentication process, which reduces login friction and minimizes password-related issues.

OneLogin is a strong identity and access management platform overall, but there are a few areas where it could be improved. One challenge is that some advanced integration and configuration settings can become complex, especially in large enterprise environments with multiple applications and custom authentication requirements.

The administrative interface could also be improved further to make navigation, reporting, and policy management more intuitive for new users. While the platform is feature-rich, certain configuration and troubleshooting activities can take time to understand. Another area for improvement is reporting and analytics. More customizable dashboards for visibility into authentication trends, access activity, and security events could help administrators monitor its efficiency.

I have been working with OneLogin for around two years.

OneLogin is stable.

OneLogin is scalable with good uptime and reliable performance, especially for standard authentication and user access management activities. Its cloud-based architecture also helps support scalability and availability for distributed and hybrid work environments.

Customer support is good.

I have seen a positive return on investment from using OneLogin, mainly through improved operational efficiency, reduced support overhead, and strong centralized access management. I also saw time savings through automated user provisioning and de-provisioning workflows. New employees get access faster because access permissions are assigned automatically.

My advice to organizations considering OneLogin would be to spend time planning their identity management architecture, application integration, and access policies before deployment. I would also recommend involving security, infrastructure, and application teams early in the implementation process, especially in enterprise environments with multi-cloud applications. I would rate this product an 8 out of 10.

My main use case for OneLogin is single sign-on and MFA enforcement with centralized user access management across SaaS applications.

A specific example of how I use OneLogin for single sign-on and user access management in my daily work is that we use it for new employees to provide one secure login for applications like Microsoft 365, VPN access, and internal SaaS tools while enforcing MFA policies based on user roles and access location.

OneLogin made a difference for us during the remote work expansion because it centralized authentication and MFA policies across cloud apps without adding too much complexity for users.

The best features that OneLogin offers for my team are the single sign-on experience, adaptive MFA, centralized access management, and the large number of pre-built integrations with SaaS applications. The Smart Factor adaptive authentication feature is especially useful because it adjusts security management based on login risk and user behavior.

The adaptive authentication feature makes things easier or more secure for my team because Smart Factor adds extra verification only when login behavior looks risky, so users are not constantly dealing with MFA prompts during normal day-to-day access.

The integration library is definitely one of the strongest parts of the platform, but more granular reporting and customization options would make administration even better.

Based on my experience, improvements needed for OneLogin include better granular policy controls and more advanced analytics for authentication activity, which would be especially useful for larger enterprise environments.

I have been using OneLogin for two years.

OneLogin is stable in my experience.

OneLogin scales well for enterprise environments, especially for organizations managing large numbers of users and cloud applications, and the centralized SaaS integration module makes expansion fairly straightforward.

Customer support is excellent.

Before OneLogin, we mainly used native application logins and some Microsoft ADFS, but we switched to get simpler cloud-based SSO, stronger MFA capabilities, and easier SaaS integration management.

My experience with pricing, setup cost, and licensing is that the pricing is competitive compared to other enterprise IAM platforms, and the setup was relatively straightforward for standard SSO deployments, although more advanced integration and policies required additional planning and configuration effort.

I have seen a return on investment as the adaptive login features with Vigilance AI have been useful for identifying unusual login patterns and automatically applying stronger authentication when the risk level increases. We have seen good results mainly through reduced password-related support tickets, faster onboarding, and less time spent managing user access across multiple SaaS applications. The centralized SSO and MFA management also reduced a lot of repetitive admin work for my IT team.

My experience with pricing, setup cost, and licensing is that the pricing is competitive compared to other enterprise IAM platforms, and the setup was relatively straightforward for standard SSO deployments, although more advanced integration and policies required additional planning and configuration effort.

We evaluated Okta, Microsoft Entra ID, and Ping Identity before choosing OneLogin.

The advice I would give to others looking into using OneLogin is to plan your application integrations and MFA policies carefully from the beginning because OneLogin works best when access management and authentication workflows are standardized early on.

Overall, OneLogin has been a reliable and user-friendly IAM platform that helps simplify SSO and strengthen MFA adoption without creating too much complexity for users or administration. I would rate this product an eight out of ten.