OneLogin Reviews

OneLogin is primarily used to manage user access. OneLogin has been integrated with SSO and MFA for cloud tools and internal tools, which has made login simple and secure.

The easy single sign-on with OneLogin for many applications is beneficial, and the MFA option provides good security while working well with cloud services such as GCP and AWS.

The best features OneLogin offers include a strong MFA option for security and excellent compatibility with all cloud services. OneLogin integrates with all tools, which helps manage access to different environments easily, especially in cloud and DevOps work.

The MFA option in OneLogin stands out because the features currently in use are very useful, integrating with all internal applications and other third-party applications and adding strong security with options such as push notification and OTP authentication app. The setup was simple for users and helps protect cloud accounts from unauthorized access.

OneLogin has positively impacted the organization mainly by saving time for the IT team. Previously, password reset issues were a challenge, but now everything is enabled through MFA and single sign-on with all applications, which saves considerable time and enhances security.

OneLogin could be improved with simpler user management features, though the current interface is relatively straightforward to use.

OneLogin has been in use for two years.

Overall, there is satisfaction with OneLogin, and based on the current experience with the product, it would be recommended to other users.

My main use case for OneLogin is for security enhancement and account management. I use OneLogin mostly for security enhancement as well as users' account management, which includes the management of the client's accounts as well as team members' accounts.

The features I appreciate most about OneLogin involve the multi-factor authentication, which I consider one of the best features because it provides many options for increasing system and tool security. This helps us to see that our data and accounts are protected from threats, hackers, and unauthorized access. The MFA also helps us to add extra layers of security to the account.

The second feature I want to discuss is the integration feature; in this integration, many other features are exported from other tools and built into this single tool, which helps us to reduce manual effort and limit errors that could be caused by manual data exchange. All the information is gathered in a single place, and OneLogin has become a solution for all security purposes as well as the integration of other tools we use.

When we talk about security and usability, SmartFactor Authentication is a valuable tool because it helps in enhancing the tool's security. One of the valuable things I see is that it can detect errors and risks in authentication and provides advanced security for the tool, meaning that it can detect higher-risk logins and prevent unauthorized access. It also identifies non-compliant users and detects unsafe places, including anonymous IP addresses, which may be used by spies or phishers, providing strong security for the system.

OneLogin has positively impacted us in many different ways, particularly in terms of cost, as our costs have been reduced compared to what we have been spending.

OneLogin can be improved mostly by maintaining and upgrading it. Everything is running well currently, so I have not identified any required improvements at this time.

I believe the initial setup should be more straightforward. The initial setup should include all instructions in a tour video, so when someone is running it, they can watch and realize how things are done, not only regarding domain booking but also having posted videos daily about added features. This would make it easier for the person installing initially to know what should be done and what has been added. This would help anyone, regardless of their coding skills, to learn how to install it through video explanations.

I have been using OneLogin for one year.

I purchased OneLogin through the AWS Marketplace. I would rate this product nine out of ten.

OneLogin is our main identity and access management tool. We use Active Roles for user provisioning, which allows us to delegate the provisioning to other people. OneLogin manages user access permissions and includes creating mailboxes.

OneLogin's best features are the whole package, which includes the combination of the integration with Active Directory, user provisioning, and the graphical user interface. OneLogin has positively impacted our organization by saving us money because we automated a lot of things with One Identity.

OneLogin could be improved with more add-ins for integration with Entra ID and Exchange Online. I would appreciate more options to add to One Identity, such as Entra ID provisioning and Exchange Online mailboxes directly, and maybe integration with Graph.

I have been using OneLogin for about 10 years.

OneLogin seems stable to me. There are sometimes CPU usage peaks when certain scripts perform, but overall, it is stable.

I do not manage OneLogin's scalability, as another department handles this.

I have not had any experiences with customer support, but one of my colleagues did, and he was quite satisfied.

Positive

Before OneLogin, we did not have any other solution; there were just manual scripts.

I did not handle the pricing, setup cost, and licensing aspects, as they were managed by another department.

I think we evaluated other options before choosing OneLogin, but that was before my time.

OneLogin is nice and easy to use. I would rate OneLogin an eight out of ten because nothing is a ten for me; everything can be improved, and this is quite acceptable. More integration with other solutions, especially Entra ID, would contribute to a higher rating. Based on my experience, the user identity synchronization across directories functionality in OneLogin is acceptable. Regarding OneLogin providing a smooth experience for end users when they are signing in and accessing applications, end users are not really logging in through One Identity, but One Identity provides them all the necessary groups to log into their applications, so they do not notice anything. The experience is smooth. My advice to others looking into using OneLogin is to get skilled people who can work with OneLogin and who can script. My overall rating for OneLogin is eight out of ten.

My main use case for OneLogin is authentication. I use OneLogin for authentication in my organization specifically for single sign-on. My team accesses ServiceNow and home-built applications through OneLogin single sign-on.

The best features OneLogin offers include easy setup and good security. The easy setup was due to my ability to integrate with our Active Directory, which made the setup process smooth for me, and I noted the good security with its standout security feature.

OneLogin has positively impacted my organization by helping reduce issues and save time. It helped with the automation of our authentication, so it saved us from having to troubleshoot that.

OneLogin can be improved with more federation support.

I have been using OneLogin for one year.

OneLogin is stable.

OneLogin's scalability is very easy to scale.

The customer support is great. I would rate the customer support a 10.

Positive

I have seen a return on investment, with fewer employees needed.

My experience with pricing, setup cost, and licensing is that it's very easy and straightforward.

Before choosing OneLogin, I evaluated Okta.

The advice I would give to others looking into using OneLogin is to do a demo of it and try it out to make sure it will work for your organization. I would rate this review a 9.

My main use case for OneLogin at my organization is to access our SharePoint and other internal documents when it's prompting me to do a two-factor authentication.

One example is that earlier today I was trying to access the hub and in order to do so, I had to sign into my work email, which I did. OneLogin was able to step in and prompt me to do a further authentication through OneLogin app on my phone to grant me access to the hub.

I use the single sign-on feature and I use it every day.

One of the best features is how fast OneLogin prompts you to submit a number.

The speed of the prompt grants me the ability to access my internal resources faster, which then makes me be able to work quicker and more efficiently.

OneLogin has impacted our organization by making work efficient for people by granting them easy access and logins.

In terms of security, I have been able to have all my information on lockdown more.

It was so easy to integrate OneLogin single sign-on feature on my third-party authentication provider.

I was pretty impressed with OneLogin's ability to provide a seamless end-user experience for signing in and authenticating to needed applications.

I think OneLogin works well the way it is.

I have been using OneLogin for the three months I have been employed at One Identity and it has been great.

OneLogin is stable.

OneLogin's scalability is very good.

OneLogin's customer support has been great. I would rate OneLogin's customer support a 10 out of 10.

Positive

I did not use a different solution before OneLogin.

I would encourage others looking into using OneLogin to explore the entirety of the app.

I give this product a rating of 10 out of 10.

My main use case for OneLogin is centralized identity and access management, primarily for enabling single sign-on and MFA across cloud applications like Microsoft 365, Salesforce, and internal business tools.

For single sign-on or MFA in my daily workflow, we use OneLogin to give employees one secure login for applications such as Microsoft 365 and Salesforce. MFA automatically triggers when users sign in from unmanaged devices or new locations, which has made access management much simpler for the IT team.

The best features OneLogin offers include easy management of SSO, adaptive MFA, Smart Factor Authentication, automated user provisioning, de-provisioning, and strong integration support for cloud and on-premises applications, which really helps simplify identity management and improve security.

Smart Factor Authentication in OneLogin has helped us reduce unnecessary MFA prompts by applying extra verification only for risky logins. Automated provisioning saved a lot of time by automatically creating and removing user access based on HR or Active Directory changes.

OneLogin has positively impacted our organization by improving security and user experience by simplifying access to business applications through single sign-on while also reducing password reset tickets and manual account management for the IT team.

After implementing OneLogin, we saw password reset tickets drop noticeably because employees could access most applications through a single login and automated provisioning reduced manual onboarding and offboarding work that previously took the IT team hours each week.

Overall, OneLogin has been a reliable identity management platform for simplifying SSO and MFA across multiple applications. It is especially useful for organizations looking to reduce password-related support issues while improving access security.

OneLogin could improve its admin interface and troubleshooting experience because some configuration and error logs can be difficult to track during complex integrations or provisioning issues. Better documentation and faster support for advanced cases would also help IT teams manage deployments more efficiently.

One area I would appreciate improvement in is reporting and audit visibility because pulling detailed user activity or troubleshooting authentication failures can sometimes feel less intuitive than it should be, especially in larger environments.

Better customization and clearer workflow for complex conditional access policies in large enterprise environments are needed. I advise starting with a small pilot rollout first and ensuring that your identity sources such as Active Directory or HR systems are properly organized before enabling automated provisioning.

I have been working in my current field for one year.

My main use case for OneLogin is to provide secure single sign-on access to multiple applications for our users. This simplifies user access by reducing the need for passwords and helps decrease password-related issues. OneLogin also manages user provisioning and de-provisioning to ensure users have the right access at the right time. Additionally, it implements multi-factor authentication and policy control to enhance security.

A specific example of how my team uses OneLogin for single sign-on and user provisioning in our day-to-day work is when we onboard a new employee. We use OneLogin to quickly provision their user account across multiple applications. We create their account in OneLogin, which automatically grants them access to email, the HR system, and project management tools without needing separate logins. This saves time and reduces errors compared to manual account creation in each application.

We also enforce security policies such as multi-factor authentication for sensitive applications. This provides protection against unauthorized access and enhances our overall security posture.

OneLogin has positively impacted my organization by centralizing identity management and enforcing strong authentication policies such as MFA. It has streamlined user access, allowing employees to log in once and access multiple applications, which boosts productivity.

The best features OneLogin offers are single sign-on, multi-factor authentication, and user provisioning and de-provisioning automation.

What makes the multi-factor authentication and provisioning automation stand out to me is the support methods such as SMS, authenticator apps, and hardware tokens, which give flexibility to users and administrators. It is easy to configure with policies that can be applied based on user roles.

The user-friendly interface makes it easier for IT teams and end-users to manage access and authentication.

OneLogin can be improved in several ways. The initial setup process can be easier.

The documentation could be more comprehensive and easier to navigate, especially for complex integrations. Step-by-step tutorials and troubleshooting guides would help users resolve issues faster without needing to contact support.

I have been using OneLogin for approximately nine to ten months.

OneLogin is stable.

OneLogin is quite scalable.

Before using OneLogin, we were not using a different solution.

OneLogin has reduced the time required for user productivity by approximately forty to fifty percent.

The impact of enforcing MFA at the desktop level, regardless of online or offline status, on my security protocols is significant. When offline, it strengthens security by ensuring that only authorized users can access the device. It reduces the risk of unauthorized access if a device is lost or stolen, as credentials alone are not sufficient. This approach maintains compliance with strict security policies and regulatory requirements.

I have seen a return on investment with OneLogin, as time has been saved.

I was not on the team that handled pricing, setup cost, and licensing.

Prior to choosing OneLogin, we did not evaluate other options.

My impression of the user identity synchronization across directories functionality in OneLogin is that it is generally reliable and efficient. It supports syncing across multiple directories such as Active Directory, LDAP, and cloud directories, which helps maintain consistent user data.

My impression of OneLogin's ability to provide a seamless end-user experience for signing in and authenticating to needed applications is that it offers a smooth and user-friendly sign-in experience through its SSO capabilities. Users can access multiple applications with one set of credentials, which reduces password fatigue and support calls.

I have not used the single sign-on feature with third-party authentication providers.

My advice to others looking into using OneLogin is that it is a very good platform that you should definitely consider. I would rate this product a nine out of ten.

My main use case for OneLogin is to simplify and secure access management across multiple applications. We primarily use it for single sign-on so users can log in once and access all the tools they need without remembering multiple passwords.

Using OneLogin for single sign-on has definitely made a positive impact on both our users and our team. It has made daily work much easier since users no longer need to remember multiple passwords or log in to different systems separately. It has significantly reduced our login-related issues like password resets and account lockouts, which used to take a lot of our IT team's time. As a result, productivity has improved, and users can focus more on their work instead of dealing with access passwords.

One additional benefit I would like to highlight is the improved visibility and control for our IT team. With OneLogin, we can easily manage user access from a central place, which makes onboarding and offboarding much faster and more secure.

Overall, OneLogin has had a very positive impact on our organization. It has improved both efficiency and security across our systems. One of the key outcomes we have noticed is the significant reduction in login-related issues such as password resets or account lockouts, which has reduced the workload on our IT support team. At the same time, employees are able to access the tools they need much faster, which has improved overall productivity.

While we don't have exact numbers to share, we are definitely seeing noticeable improvement in several areas. For example, the number of password reset requests and login-related support tickets has gone down significantly since implementing OneLogin. Our IT team spends much less time handling access issues, which allows them to focus on more strategic tasks. We also observe faster onboarding and offboarding processes, which has improved overall operational efficiency.

The best features OneLogin offers are improved productivity and user experience. Multi-factor authentication adds an extra layer of security, helping protect sensitive data and reduce the risk of unauthorized access.

Our experience with multi-factor authentication in OneLogin has been very positive. Initially, there was a small learning curve for some users, but overall the adaptation was quite smooth. The setup process is straightforward, and once users understood the importance of the extra security step, they adapted quickly. From a security perspective, we have definitely seen improvements. It has significantly reduced the risk of unauthorized access and added an extra layer of protection for our sensitive systems and data. This has given both users and our IT teams more confidence in our overall security.

Overall, our experience with OneLogin has been very positive, but there are a few areas where it could be improved. One area is the user interface, which could be made more intuitive and modern, especially for new users who may need some time to get familiar with the platform.

One area of improvement would be to enhance the customization of features, especially when it comes to access policies and user workflows. This would allow an organization to tailor the platform more closely to their specific needs.

We used single sign-on, multifactor authentication, lifecycle management, and connectors.

When we rolled it out, adoption was very quick. We migrated our email and other things to OneLogin, so adoption was very quick. The gateway became OneLogin, so if you wanted to get your email or anything else, you had to go through OneLogin to get it. It was quick and easy once we turned things on. Even the engineer who assisted us was very helpful. Once we turned it on, the users seamlessly started using OneLogin. They were redirected every time from others, and that ensured that there were no loopholes in what we were implementing.

We had a single pane of glass for access management across the organization, but the caveat is that for managing users provisioning and deprovisioning, apps have to support that feature. This single pane of glass was very important because we eliminated ghost accounts that were not being used. We had no idea about them. After implementing OneLogin, when a user left, the deletion used to happen everywhere, so the licensing cost and all those things came down. Audit logs came in one place, so we had all the control. That improved our visibility a lot.

The single pane of glass for access management enabled collaborative work between IT and Security. It simplified a lot of information for Security, and for IT, it simplified their setup process. For example, they would set up automatic provisions for emails, security training, etc. They would then just set up the user on OneLogin, and automatic provisioning would be done for them. When a user left, the user was removed automatically. That cleaned up things for us and improved processes.

OneLogin 100% helped to free up time for our IT team. The main work we did was setting up automatic provisioning. We reduced our time from five to ten minutes in creating a user to doing it in an instance. For example, creating a user and assigning it on OneLogin to a department, such as IT, automatically moved them to groups and email groups on Gmail. That was no longer manual. They were just writing out the information that was given, and in the backend, it got mapped correctly to what was needed. That saved time for us.

OneLogin enabled us to securely manage a growing user base or more applications with a smaller IT staff. After implementing OneLogin, we just had to work on one main platform. We did not fully need administrators for other systems.

We worked in a hybrid environment. Because OneLogin was available everywhere, it improved the user experience when working remotely. It was a secure way to get to applications. They went through the OneLogin system to get to their apps. However, when everything is under a single pane of glass, there is a risk. If one user gets breached, we have a problem there. For example, I am an administrator, and my account can be breached. The mitigation would be setting up MFA. We needed to put such checks and balances.

The single sign-on and the fact that we can integrate everything in one place and control from there were valuable features of this solution. The single sign-on worked very well. Lifecycle management was a big feature for us because we just had to provision in one place for the supported apps and everything else that we needed. It worked well in our case.

One issue was related to the downtime. They have downtime twice a year or once in six months. During the downtime, the SSO page did not come up. When users wanted to get to their email, they were redirected to the OneLogin page, but the page did not come up, and MFA and logins failed. It completely crippled us. In those moments, people did not want to hear about a single pane of glass. We did try to solve it, but it caused issues. Their uptime is 97% or 98%, but most companies prefer 99.9% uptime.

We have had it for about a year.

It is very good when it is up. When it was down, they would give us notice, but sometimes, the platforms would not open, and sometimes the connections would not complete. When we clicked on a connector, it sometimes took a lot of time to get through to the network. Those issues were there.

We started with 500 users and went to 1,500 users with no changes needed. It worked out well in that sense. Our organization has only 1,500 people. It is not too big.

When we were deploying, we had a dedicated engineer, and I used to talk to that person directly. That was very helpful. Once we moved to ticketing, the support was a bit slower. When we had issues, we created a ticket, and there was a lot of back and forth. The times when there was no availability or there was downtime were not acceptable. Those are the main issues for us.

Neutral

We were not using any other solution.

In terms of the deployment model, it is not on-premises, but it connects to Active Directory. In our use case, we did not have Active Directory. Our setup was fully on the cloud. They connected it to our core systems. Our HRMS system and our email system were the main systems we wanted to connect OneLogin with.

The initial setup was very easy. With API keys, we could add the users with one click from the Gmail system. It was very simple for us to get that going. 

It took us a couple of weeks. OneLogin is good if there is a connector, but we did not get enough connectors from them. For example, we did not have a connector for our ERP. When we did not have a connector, we ended up building it because we were a software company. That delayed things for us.

We used OneLogin's implementation services. We had one person for its implementation.

In terms of maintenance, once we set it up, it was good to go. 

It was cheap in the beginning, and then it became very expensive. We were initially charged $2 per user per month, which was fine, but by the second year, they increased it to $5 per user. That became very expensive for us because we had about 1,500 users. At $2 per user, it comes out to be $3,000 a month, which is $36,000 a year. If we move to $5 per user, it comes out to be $7,500 a month. That made its cost so high. That is why we removed the product because the cost was high. Also, it was communicated to them. We did not expect a jump of over 100%. That became an issue, and then we had to go through a lot of negotiations, but in the end, it was not feasible for us.

We tested Okta and JumpCloud. We found OneLogin to be the best because of pricing as well. 

In terms of features, OneLogin was pretty much the same as Okta. Okta was the leading one that we were looking at. One thing that we wanted in OneLogin, but it was there in JumpCloud, was device access. We wanted device access. We wanted to be able to log into machines through OneLogin.

To those evaluating this solution, I would advise making sure that what they need out of the box is there. For example, our ERP's connector was not there, so we lost a lot of time trying to get that done. We had to go back and forth with them.

OneLogin has a feature called mapping. If mappings go wrong, the application can destroy a lot of things. For example, if you have a mapping that allows you to delete users automatically, and you make any change to that, it can go and delete. It can delete users in the live environment, such as Gmail. Because it is automated, it automatically starts removing users. It happened to us because there was no test environment. We did get one, but such things caused a lot of issues.

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

We use OneLogin by One Identity to provide SAML authentication and single sign-on for all of our SaaS apps.

OneLogin by One Identity helps us onboard new users really quickly and get everything up to speed super fast. It has helped free up about half of our time through its automation features.

The directory integration and SCIM provisioning are probably the best features compared to competitors. These are the two things I have found to be most valuable.

There have been some outages over the years. The uptime has not been great recently, with some outages lasting six, seven, or eight hours. Improvement in the stability of the infrastructure would be beneficial.

I have been using OneLogin by One Identity for about three and a half years.

The stability has been an issue, with some outages lasting several hours, which impacts our work.

It's pretty scalable. We know it can handle up to maybe two hundred thousand users, and there's no limit on the number of applications we can integrate. Overall, it is very scalable.

The quality of support is okay. It's not great, but it's not worse than other companies.

Neutral

In other jobs, I've used Okta and Auth0.

The initial set up was probably easy since the company was using it before I started working here.

I'd rate the solution seven out of ten.