OneLogin Reviews

My main use case for OneLogin is app aggregation and SSO. I use OneLogin for app aggregation, which is utilized for a single point of access, so it is used in facilitation of SSO.

My main use case fits into my team's workflow as it reduces the work, decreases the time required, and increases the flexibility of the team.

The best features OneLogin offers in my experience are password vaulting and one-click termination to prevent unauthorized access.

Password vaulting and one-click termination have made it safer for our team, as passwords can be saved in a vault that is secured safely and one-click termination helps us remove dormant accounts, making these features very helpful for us.

OneLogin has positively impacted our organization by increasing security features and making our security wall more robust as well as preventing unauthorized access from dormant accounts, making our system safer than ever before.

OneLogin is a robust platform, but there is scope for improvement as there are some glitches, connectivity glitches, and some outages that need to be improved. The outages and glitches cause a hindrance in our work and lead to time wastage.

I have been using OneLogin for the last one year.

OneLogin is stable.

OneLogin is scalable according to our organization's needs, so it is quite scalable.

Customer support is good, but it needs some improvement.

My experience with pricing, setup cost, and licensing was good, as the pricing was not very expensive and it is manageable.

I have not evaluated other options before choosing OneLogin, as it was the first one I decided to demo, and I selected it on the first attempt only.

The features that are valuable about OneLogin are the ones I mentioned. I have noticed specific outcomes since using OneLogin, such as reduced incidents of password hacking and threats from various hackers.

User identity synchronization across directories is a good feature that I use, and it helps me identify which user has been given access to what. The user experience of OneLogin is very good, as it provides a seamless experience, although sometimes there are lags. Overall, it is a seamless experience.

HR-driven identity management plays a very important role, as whenever HR assigns a new employee a user ID, I use OneLogin for that, making it very useful and safer for us. I have saved time with this software.

OneLogin is good, value-for-money software that needs improvement on some glitches, but overall, it is a value-for-money solution. On a scale of one to ten, I would rate OneLogin an eight because of the benefits that OneLogin provides.

On-premises

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.

Public Cloud

We use it to deliver single sign-on services for both our company employees and our customers.

The main advantage is its ease of use for everyday users. Additionally, it simplifies user access management by offering a centralized platform for overseeing user accounts and third-party applications, which greatly benefits my team.

The adoption rate of OneLogin within our organization is at 100% since it's mandatory for everyone to use. During the rollout phase, there was unanimous approval and no resistance from any team members.

It serves as a vital tool for access management across our organization by offering a centralized platform. While we don't directly manage user accounts within OneLogin, they are synced from our Active Directory. Therefore, OneLogin primarily functions as a single interface for administering applications that utilize it for authentication.

OneLogin has been instrumental in freeing up time for our IT team to focus on other tasks. Previously, when onboarding a new user, we had to manually create accounts in multiple applications. However, with OneLogin, we create the account in our Active Directory, which automatically syncs to OneLogin and creates accounts in other applications. Similarly, when offboarding a user, we disable the account in OneLogin, and access to all other resources is automatically revoked. This streamlined process has significantly reduced the time required to manage user accounts. Previously, manual account creation across various platforms would take at least half an hour, whereas now it's down to just five or ten minutes.

It has empowered us to effectively manage an expanding user base and an increasing number of applications, all with a smaller IT team.

The implementation of OneLogin didn't significantly impact our user experience while working remotely. We adopted OneLogin during the transition to a remote work environment at the onset of the pandemic.

It contributed to cost savings for our organization by streamlining time-sensitive processes and boosting productivity, particularly for our IT staff. While we may not have a precise quantification in terms of monetary value, the time saved allows our team to focus on other tasks. As a relatively small organization, we don't require a dedicated Identity Manager, and OneLogin effectively serves our needs in this regard.

During my evaluation of various products, one standout feature of OneLogin that impressed me was their mobile app for authentication through push notifications. Unlike traditional methods involving rotating codes, the OneLogin app simplifies the process by sending a push notification asking if the login attempt is legitimate. If confirmed, the login proceeds seamlessly.
The primary benefit is its user-friendly interface, making it particularly accessible for non-technical users.

One aspect I particularly appreciate is their exceptional customer support whenever I've needed assistance. Their sales team has also been highly responsive and helpful in connecting me with necessary resources, although we haven't faced any major challenges.

There was a minor outage a few months ago that caused some inconvenience. OneLogin offers a Virtual LDAP feature that we utilize, although it differs slightly from traditional LDAP servers. While it hasn't caused significant issues, improvements in its functionality would likely lead to wider implementation within our organization.

We have been working with it for three years.

In terms of stability, there was a downtime incident that impacted all of OneLogin's customers a few months ago, which was frustrating as it occurred during prime business hours and lasted for a couple of hours. Fortunately, the impact on us wasn't severe because our applications are configured in a way that once users sign in and authenticate through OneLogin, they typically don't need to go through OneLogin on a daily basis to access those apps again. As a result, many of our users may not have even noticed the downtime.

OneLogin has the capability to scale infinitely, although our organization's needs are quite basic. We haven't been utilizing a vast array of features or configuring hundreds of applications with it. Therefore, I don't anticipate encountering any limitations with the services that OneLogin can provide us.

I've found that when I open a support case, I typically receive a response within a few hours, and the support team has consistently provided prompt assistance. Even when investigating issues like examining internal logs for failures, they've been able to help me swiftly. I would rate it ten out of ten.

Positive

The initial setup process is quite straightforward. Any issues I encountered were promptly resolved with the help of the support team.

I managed the deployment independently and had it operational within a day or two, although some configuration and feature familiarization took about a month from starting the trial to getting the quote approved for purchase. In terms of maintenance, whenever an application changes or a new one is added, we configure it within OneLogin. So far, we haven't experienced any issues such as applications failing or directory syncing problems due to configuration changes.

While I wish OneLogin's pricing was more affordable, their licensing model, which is based on per user, is acceptable. We renew it annually.

Before deciding on OneLogin, I evaluated JumpCloud and Okta. However, I found that the features in JumpCloud weren't as developed as those in OneLogin. Additionally, my experience with Okta's sales team was less than satisfactory in terms of configuring a trial and support. In contrast, the sales representatives at OneLogin were highly proactive and went above and beyond to assist us and earn our business.

For new users, I would recommend having someone knowledgeable about their internal directory and authentication systems. It's crucial to ensure that their systems are well-maintained and free from technical debt or complexity. The effectiveness of their OneLogin implementation will ultimately depend on the quality of their internal directory setup. Overall, I would rate it ten out of ten.

Public Cloud

Amazon Web Services (AWS)

We use OneLogin to log in to all our different systems. This means I only need to go to the OneLogin portal to access all my frequently used applications, like our CRM, Greenhouse for recruiting, Jira for ticketing, Workday for HR, Tableau for data visualization, and even Slack. It's a one-stop shop for everything I need!

The main benefit of OneLogin is its centralized design, offering easy access to everything in one place.

All of our employees use OneLogin daily to log into their applications.

OneLogin offers a centralized platform for managing access across our entire organization, which is crucial for cybersecurity. It provides robust security features that give me peace of mind, knowing that data transfers are highly secure and unauthorized access to our databases is extremely unlikely.

The single pane of glass enables collaborative work between holistic IT and security.

OneLogin has helped our IT team significantly improve their efficiency by creating a centralized platform. This eliminates the need to access information from multiple portals, saving over 50 percent of their time.

OneLogin has improved the user experience when working remotely.

OneLogin has helped increase productivity.  

OneLogin is efficient. The fact that I'm able to just have one go-to place where I can access everything in one area, so that's convenient.

I'd like it to have a customization section that displays the company's offerings, categorized by different topics. Ideally, there would be a user-friendly feature at the top allowing individuals to pick and choose the topics they're interested in, essentially creating a personalized experience.

I have been using OneLogin by One Identity for over four years.

OneLogin has been stable.

The scalability is good, and we're currently migrating our customer relationship management system from Salesforce to different software. Fortunately, OneLogin hasn't been involved in any data transfer, so I don't anticipate any hiccups or obstacles in that regard.

I rate OneLogin a ten out of ten.

OneLogin does not require maintenance.

With a good IT team, OneLogin works smoothly and it is self-explanatory. 

Private Cloud

We use OneLogin for single sign-on to provide a consistent user experience with our in-house and external third-party applications. In addition to single sign-on, we use two additional modules: two-factor authentication and self-service password reset. It's a SaaS product.

Previously, users constantly had to log in with their user ID and password. It was the same user ID and password for all these applications, but they had to authenticate when they used all the applications they needed to use daily, whether they were an employee or a student. They would authenticate into one application and bounce over to the next to log in again. That's a huge benefit that the organization is leveraging with OneLogin.

The other benefit is that we've reduced calls to our help desk for password resets. Staff and students can now reset their passwords using their enrolled two-factor device as the authentication mechanism. In the past, we were using secret questions through a self-service portal. Inevitably, they would forget their answers or type them wrong. It just wasn't user-friendly. 

We're always onboarding new students, and we can set a default profile. Each student has access to a default set of applications, but when they enroll in a class, they might get access to other applications. They're active students, and all that is happening dynamically. We use data feeds from our student integration system to determine student roles and access to applications. We don't need to do that manually. OneLogin can set up those mappings for us automatically based on their enrollment.

It helped us manage our growing user base because we can use data from our SIS and HR platform to drive secure access to applications. Before this, we didn't have the capability. Either everybody got it, or we had to provide access through a request to our service desk manually. I won't say these requests have been eliminated. Still, they have been drastically reduced because we can pull that data feed from those two record systems to provide some access, reducing the workload on the systems and the security team.

With OneLogin, we use the same validator as our login: an authenticator application or a text message. That same two-factor authenticator is used for the password reset. We've significantly reduced the number of trouble tickets and tier-one service desk calls because everyone can reset their own password.

The adoption rate is high because we don't give users a choice. When we add new applications to our portfolio, IT is part of the process on the procurement side. When reviewing a request for an application, one of the first features we look at is the single sign-on capabilities. Do they do SAML? Do they do open ID?

We approve the purchase if all those features check out because we can connect third-party applications for single sign-on. IT is part of the first step. They don't get a choice on the front end of it. IT ensures the application can meet the requirements. We protect that app with two-factor authentication.

We allow a little flexibility on user enrollment in 2FA. It requires some custom development work to make this happen because the functionality isn't native to OneLogin, but we allow a grace period for students to enroll. We didn't want to force enrollment on them right out of the gate. Brand new accounts are required to enroll. We wanted to prompt them, "Hey, here's what you need to do. You need to enroll in two-factor authentication. You have 30 days to enroll in it. Here's a tutorial telling you how you enroll." They can enroll at their leisure.

After 30 days, you don't get any more opportunities. You're forced to enroll. You can't log into any system until you've enrolled in two-factor authentication. We force it on them, but we give them a little time to ensure they have an appropriate device and they've read through the knowledge base to learn how to do it. 

Before OneLogin, we had some SSO in place. It was all custom-developed integrations by our in-house developers, but it was never the same. We had a custom SSO for each vendor. By adopting OneLogin, we could reduce the development time. It's not the developers' job anymore. That responsibility shifted to my systems integration team. It reduced the manual effort needed to provide a single sign-on experience. Now we have a true single sign-on experience with few onboarding requirements for connecting to third-party applications with OneLogin because it uses a standard like SAML or Open ID.

These days, more students and staff are working remotely. They still have the same experience they had on campus, but we're protecting their accounts with 2FA. The world was told to work from home at the pandemic's start. We didn't have two-factor before that, so COVID was a significant factor driving the push to make this mandatory for all our staff.

We do not control the network they're on, but we see authentications happening all over the place. People weren't just staying in their city anymore. They traveled to some extent after restrictions were removed and logged in from all over the country. How do we validate that these accounts weren't compromised? The two-factor helped the security side to ensure these authentications are legitimate. At the same time, they provided a secure environment for telecommuting. They won't be denied access to those systems because their account was compromised.

I believe we've saved money, but I'm not sure I can quantify it. In August, we'll review our help desk tickets for password resets. That's one area where I think we'll save money because our calls have decreased. I don't know how much they've declined, but our call volume should be down.

We can also review our application use through the OneLogin portal, which could save us some money on under-utilized licenses. For example, we might have 100 licenses for an application, but only 25 users access it annually. It gives us the data on who's using the application and how frequently to help us make these decisions. That said, we don't have that data yet to quantify how much we're saving, but we will review it after using the platform for a couple of years. As the contracts start coming up for renewal, we can use that data from OneLogin to renegotiate better contracts with vendors.

In my role, the most valuable features are two-factor authentication and self-service password reset. The most helpful feature for the institution as a whole is probably the single sign-on. As an IT director, I care about security and ease of use. 

OneLogin provides a single pane of glass for events that happen within our organization on applications that are connected. We can see logins, sign-outs, password changes, two-factor prompts and failures, failed logins, etc. It's a crucial feature. We scraped those logs and sent them to our SIEM and SOC to look for anomalies and vulnerabilities. Having them in a central place in OneLogin streamlines that process for us.

We want to review those logs proactively. In addition to OneLogin's risk analysis, we want to pull it into our SOC and have them take a deeper look. They pull in additional data points to see anomalies in OneLogin, Office 365, and the network. They can piece together some events that we need human eyes on. Having them in one spot makes it easy to get to that point.

We use Webhooks for two items. One is the enrollment grace period. The other one is to capture data in our SIEM for our SOC to review. Those are two development Webhooks that we're leveraging. We still run some custom items on our servers to leverage those Webhooks. One is the enrollment grace period. Webhooks can use the data from OneLogin and manipulate it on-premise. That's invaluable. We could not have done our enrollment process without that Webhook. It wouldn't have been as nice of an onboarding experience for our users. It would've been more troublesome for them.

Webhooks freed up a tremendous amount of time. We looked at it from the perspective of maintaining this long-term. Enrollment in 2FA isn't a one-and-done. We have students coming every day. It's not like we're done once we get everybody enrolled. Our onboarding is never-ending. There was no way we could maintain that on a user-by-user level. It was going to be a manual process. Webhooks allowed us to provide that pleasant experience without needing to manage this in the future.

We didn't initially have SmartFactor when we started the contract, but we saw the value. We don't feel comfortable prompting our users to validate using their two-factor enrolled device each time they log in. We only use SmartFactor when a change in user behavior is detected. For example, maybe they're logging in from a new device or an IP address the system hasn't seen before, which raises their risk score. That's when we prompt for that authentication, for that two-factor authentication.

If you're sitting in your office and logging into the same computer simultaneously from the same IP address, there's no need to keep prompting you for the two-factor authentication throughout the week. We only ask for it when something changes. For example, if you take your computer to a coffee shop, you will get prompted because that's unexpected user behavior that the system hasn't seen. 

It's a good compromise between security and usability. We haven't moved to password list technology, but OneLogin has the capability. We still require a user ID and password as the front entry, followed by two-factor authentication as the validation that you are who you say you are. 

It has a risk score based on user behavior anomalies, like login location, time, and device, usability and security, and more. There's a good balance. The two-factor authentication offers protection, but we don't want to bombard you with two-factor prompts when you're just trying to do your job. We only want to do it when something has changed about your login behavior.

We use the OneLogin Desktop feature in a limited capacity for some self-service kiosks around the organization for payment stations. Students can make payments using a single sign-on via the desktop. Because the application is doing authentication behind it, we haven't extended the OneLogin Desktop to staff or student desktops. One of the main reasons is there's not a great way within the service portfolio that OneLogin has to use the desktop but pick and choose what applications will do single sign-on.

We've been a OneLogin customer for several years now. While I like the platform, there have been some challenges. A great example is the amount of work needed with that webhook for the enrollment user experience. This functionality is native to some competing products. That's one area where we've leaned on our account rep over the years. They shouldn't rely on the customer to make this experience better. This is one feature request that hasn't been implemented yet.

At the same time, they've implemented other features we've requested. One is the ability to use a personal email address as a factor. Initially, they didn't have that. We pushed hard on our account team for about two years before it was finally released. 

It's a give-and-take. Some of the product's features aren't perfect, but we've had some success pushing fixes to the development team that needs to happen. They've done a decent job. However, there are some fixes that they don't have an interest in. A lot of what I described was before OneLogin was acquired by Quest/One Identity. Things have changed. It doesn't feel like they're driving the product as OneLogin was. It may be because it's a new product to them, and they're still trying to get the lay of the land, process feature requests, etc., but it's not moving as fast as before. 

We've been experiencing some pain points since the acquisition. For example, there have been some outages we didn't see previously, which are a big topic with my executive team. You have hundreds of applications relying on this service for login. If the service is unavailable, nobody can log into these applications. The issues have high visibility. It's gotten better, but it's still there. It raises questions about whether One Identity can support the platform they've acquired. How are they enhancing the product? And how are they supporting the product and the service in the future? Those are two essential questions. There are also lots of nice-to-haves, but that's the case with any product. 

I have been using OneLogin since 2019.

I rate OneLogin's support a seven out of ten. My evaluation of OneLogin's support depends on whether we're talking about before or after the acquisition by One Identity. Initially, we didn't have any problems. They were quick to respond, and it was easy to get ahold of them. When we first started using OneLogin, I would rate the support a nine out of ten. 

We've experienced some pain points since the acquisition. When we had a service outage, we had trouble getting through to someone. They're trying to streamline this and provide customers guidance on communication channels. At one point, their phones were offline when they had an outage. Their tier-one support portal to escalate a ticket was unavailable. It was the perfect storm. That was a terrible experience.

Since then, they've tried to break some of those dependencies, so you can log into the portal when there is an outage. They've updated their status page, so it isn't dependent on the rest of their services. It is getting better. One of our challenges is determining whether an issue is a feature request or a bug. Our account manager tells us something is a bug, while the support staff keeps telling us it's a feature request that will be on the roadmap. Indeed, it's a bug that needs to be addressed. It's an issue. The product's not doing something, and we're not asking for something new. We've had to get our account manager involved a couple of times in that scenario. I can think of two cases we've had for that.

Neutral

In 2017, we bought a product that seemed like it would solve all our problems on paper. It was going to be the greatest product ever. However, when it came time to implement it, we learned that the product we were promised didn't exist. It was a challenge to get everything to work. It took us six months to onboard a single application for single sign-on. That is no exaggeration. When we moved to OneLogin, we could onboard that application in minutes. 

We purchased another product, but we ultimately realized it wasn't a good fit for us as a customer or for them as the provider. They were just as frustrated as we were that they couldn't perform to our level of expectations even though we're talking about a basic core service they couldn't provide. Before that, everything was developed in-house. We had custom-developed solutions to make single sign-on work.

Setting up OneLogin is straightforward. Their onboarding is streamlined, and the onboarding engineer was knowledgeable of the product. We were up and running on our basic apps quickly, and they were responsive during the onboarding process. We had a nice onboarding experience with checklists as we went through and got the service operational. The onboarding experience was great.

We had three system admins from our organization. It was me and two of my employees. After deployment, it requires little maintenance. We use the product rather than maintain it. We add new applications to the portfolio, look at the logs, and check in on some of the processes that we built around it. 

We worked with an implementation consultant, a professional services manager, and an implementation consultant from OneLogin. Once our contracts were all signed, we had our account manager who brought in the onboarding engineer. We scheduled regular calls with that onboarding engineer to work through a checklist of what we needed to do to start leveraging the service in production.

I don't know what will happen at the end of my five-year contract. It's no longer purely OneLogin. Now it's OneLogin by One Identity, so I don't know about their current pricing model. Price was a deciding factor when I bought the product several years ago. When we compared products, OneLogin had a price advantage over similar services. However, we found that their competitors could do things OneLogin couldn't.

We were happy with the price we got when we signed up, but I don't know what will happen when the time comes to renew because it is a different company now. We haven't seen any pricing models or had that discussion yet. My renewal is a year and a half away. It's worth what we're paying for it. There's no way we could provide the level of service for cheaper or try to do the same in-house. 

We evaluated some of the competitors in the market and got a recommendation from another college in our state that we work with on other projects. They were using OneLogin and gave a glowing recommendation. That's how we ended up finding OneLogin and doing a demo. We also talked to some similar service providers out there.

Public Cloud

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.

Public Cloud

Our goal was to eliminate our on-site Active Directory and legacy Windows infrastructure since we operate solely on Macs. We considered two options: one that precisely aligned with our needs, and another that functioned more like a public solution. Ultimately, I chose OneLogin due to its enterprise-grade features and the professionalism of its representatives. It provided a seamless transition to the cloud, consolidating all our access needs onto a single platform.

Since implementing OneLogin, managing user accounts has become significantly streamlined. We no longer need to create and delete four separate accounts for each new user – a major advantage for an international school like ours, where student and staff turnover can be dramatic. In August, we might see 50 new students, while 30 may leave in October. Managing individual accounts across every platform was time-consuming, hindering our ability to improve workflows and automate processes. OneLogin simplifies this task, making user management faster, easier, and significantly more productive.

Many users forget their passwords, especially after an extended break like a three-day weekend. This leads to frequent password resets in less tech-savvy organizations. To simplify this process, we rely on OneLogin. With a single password reset, users can regain access to all their applications, making it significantly easier for them. Initially, there was some resistance from IT staff, but the convenience of one password won them over. Now, with macOS's desktop Single Sign-On, we're leveraging OneLogin even further. We use it to authenticate users to the radio server, lab machines, and shared workstations, and the upcoming Mac desktop SSO will streamline direct logins to individual Macs as well.

OneLogin provides a single pane of glass for most of our needs. It functions like a dashboard, giving me all the key metrics I need to see, such as the number of logins attempted and the number of failures. This allows me to quickly identify trends, like increased failures during holidays, and understand the reason behind them. Additionally, OneLogin offers the potential to integrate more frequently used apps and generate valuable reports. While it doesn't provide complete visibility due to the inherent privacy features of Macs, it covers the majority of our login activity. For deeper insights and troubleshooting Mac-specific login issues, I do need to utilize the Mac management tools directly.

The single pane of access management facilitates collaboration between IT and security, even when, as in my case, those roles are combined. The granular control allows us to tailor user access to the system's functionalities based on the specific needs and workloads of both IT and security personnel, enabling the creation of different user groups with varying levels of access.

OneLogin has saved us a tremendous amount of time, especially in account management. Creating and deleting accounts no longer eats up half my day. I used to spend countless hours on the phone and manually handling these tasks, but now it's a breeze. The workload has drastically reduced, and the process is incredibly streamlined. I simply create a user, and everything else takes care of itself automatically, from licensing to configuration. It's that simple!

During the COVID pandemic, we had a surge in remote workers. Provisioning accounts for essential tools like Teams became cumbersome. To streamline the process, we started to implement automation for Office 365 through OneLogin. This automatically created accounts in Azure, eliminating the need for manual account creation. Onboarding new users into various applications became quick and efficient. Instead of assigning licenses individually, a single organizational setup granted licenses to all 650 users instantly. This streamlined approach saved us considerable time and effort.

As a non-profit organization, our focus isn't on generating or saving money for ourselves. However, in terms of regular expenditures, including capital expenditures, we've seen significant cost reductions since switching to OneLogin. This is primarily due to eliminating our former Windows infrastructure, including legacy servers and associated maintenance requirements. We no longer need to hold spare parts on-site or staff a large IT department to manage and operate these systems. Overall, OneLogin has contributed to substantial year-over-year savings within our budget.

OneLogin's ease of use is a game-changer. No need for a dedicated team – a single person can manage everything effortlessly. It streamlines account creation across diverse systems, a godsend for small teams like ours. Back then, we were just two; now, we're four. Setting up accounts for 600 students across seven or eight platforms used to be a slog. But with OneLogin, it's a breeze. Just configure a few connectors and bam, everything hums along smoothly.

Simplicity is the most valuable part of OneLogin. It is easy to use. The documentation is well done and the integration with other applications is simple.

While I initially used OneLogin's desktop feature to extend SSO, I discontinued it two years ago due to limitations. Firstly, the feature lacked day-one support for new macOS versions, forcing me to postpone system updates until OneLogin released a compatible update. Additionally, our adoption of Jump Pro for mobile device management necessitated the use of their native Jump Connect product for broader access management, rendering the OneLogin desktop feature redundant.

We're using Meraki, and even though the OneLogin integration works fine, it doesn't pass one specific tag that Meraki just ignores. I've been back and forth with both Meraki and OneLogin support trying to figure it out, but they keep blaming each other.

We have been using OneLogin for almost four years.

I would rate the stability of OneLogin a ten out of ten. We are in the EU region and we have not had any stability problems the entire time we have been using it.

OneLogin is cloud-based and super easy to scale and streamline. I would rate the scalability a ten out of ten.

Since implementing OneLogin, I have only required technical support four times. The solution is well documented and we can find answers ourselves for the most part, but for the times I have used their support, they have been good.

Positive

Our OneLogin account manager, along with a couple of their technicians, assisted us with the initial setup. We handled the basic configuration ourselves to our specifications. However, for some specific use cases and unique requirements that necessitated process automation, we enlisted their expertise. I also have a good understanding of the custom connectors, and we're comfortable managing those on our own. After that initial collaboration, I didn't require much further assistance. The remaining configuration steps are well-documented and straightforward.

After approval and the initial calls, the deployment took less than 24 hours to complete.

The deployment involved one person from our organization and two people from OneLogin.

We've seen a significant return on investment in terms of the time OneLogin has saved us. It has streamlined our workflow, making it much simpler and more efficient. This allows us to focus on other projects and priorities, knowing that OneLogin is handling account deletion and suspension automatically. By automatically suspending or deleting accounts when users are removed, OneLogin helps us maintain top-notch security and stay within our security margins.

OneLogin's pricing, from the perspective of the education sector, seems quite reasonable for the value it delivers. While we secured a favorable deal at implementation, I'm unsure if their pricing structure has changed since then. Fortunately, our long-term license ensures price stability, as our recent three-year renewal at the same cost confirms. I understand, however, that pricing for more traditional businesses or large enterprises might differ.

We also considered JumpCloud, as it offered some Mac management features alongside its core functionality. However, compared to OneLogin, the solution was still in its early stages of development.

I'd rate OneLogin by One Identity an eight out of ten. It wasn't on my radar before I joined this organization, but I championed its implementation, and even looking back five years later, I stand by that decision. It's a major time-saver and convenience enhancer for everyone here. The workflow is intuitive and accessible and rarely requires support intervention for basic tasks, which makes us all much more efficient.

OneLogin is deployed in one location. We are a K12 school with everything from young kids to high school students. It is one building with multiple divisions with 650 users. We have two people in IT with full access to OneLogin and two people with limited access to reset passwords.

Maintenance is minimal. Our main responsibility is to ensure application tokens like those for Office remain authenticated. Otherwise, provisioning will halt. This is solely on us; OneLogin isn't responsible for token management. Last year's dashboard update was primarily aesthetic. While the new interface is attractive, it offers minimal functionality. It simply displays the main provisioning screen, which fulfills their basic requirement. Essentially, OneLogin's end is covered, leaving the onus of maintaining app connections squarely on us.

While I recommend OneLogin, it's essential to proceed with caution. Make sure it aligns with your specific needs. Due to its extensive feature set and constant updates, OneLogin can be overwhelming, especially for users who lack a clear vision of their desired outcomes. Simpler, more limited products might be better suited for such scenarios, as they avoid information overload while offering focused functionality.

Public Cloud

The solution allows the user to search logs based on a specific time. It is the main feature.

The tool must be made more robust.

I have been using the solution for two to three years.

The product is scalable.

The solution requires maintenance. One person is enough to maintain it.

The price of the product is okay.

The adoption rate of the solution in our organization is good. There are no big challenges. I restrict access to just one interface. We only use one application. There’s no interaction between the product and other applications in the environment.

In one year, the product has helped to free up almost a month’s time for our IT team. The solution works okay. There was no problem with the user experience when working remotely. The solution has helped our organization to save money.

We use one account for managing the systems. We improve law enforcement using the application. The legal department requires some information from this application, and we provide it to them. I maintain the servers. I work in DevOps.

Overall, I rate the product a nine out of ten.