My main use case for OneLogin revolves around application integration and user authentication. I primarily utilize it to implement Single Sign-On across internal and external applications, which significantly simplifies the login process for users.

I use OneLogin for Single Sign-On with an internal project management tool that our team uses alongside a customer relationship management CRM system. Before integrating OneLogin, users had to remember separate login credentials for each application, which was a hassle and often led to frustration. The process has become much smoother with login pages, authentication, and access granted.

The best features OneLogin offers are Single Sign-On, multiple Multi-Factor Authentication, and user provisioning.

Multi-Factor Authentication is generally useful for adding an extra layer of security, which is crucial, especially for the sensitive nature of the data we handle.

OneLogin has had several positive impacts on my organization in several key areas. Single Sign-On and Multi-Factor Authentication have been beneficial. Additionally, the user authentication has been improved remarkably. Before OneLogin, our team was burdened with managing multiple credentials, but now it is much more efficient.

Since implementing OneLogin, I have been seeing a significant reduction in login-related support tickets, approximately a 30% decrease.

I do utilize Smart Factor Authentication with OneLogin. I find it to be a really valuable feature for balancing security and usability.

OneLogin can add more analytics and reporting and integrate with more third-party applications.

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

OneLogin is stable.

OneLogin is a good scalable product.

Until now, it is great. I have not used their customer support.

The initial setup was not that difficult. I have used it, and while it was a bit tricky for some time, it was manageable.

The setup was good and easy. I am still using the free trial, but I will be purchasing it.

Other organizations can use OneLogin, but they can also refer to Okta. I have not used Okta until now, but I am hearing that it is more great than OneLogin.

I am still using OneLogin, so I am still exploring the app and need some more time.

The experience has been smooth and quite positive. My review rating for OneLogin is 8.5 out of 10.

When we have multiple environments for our customers, OneLogin by One Identity helps us create policies based on device, network, and role. For example, when an engineer wants to access the Azure portal via SAML SSO, we provide access according to their role. When they need VPN access via RADIUS or LDAP, we grant access based on network requirements.

The multi-factor authentication feature has helped our company, which is an IT service provider, secure admin and privileged accounts. When our technicians access client systems remotely, we need to provide them with secure and privileged account access. It has improved our compliance by allowing us to meet client requirements for MFA on all sensitive systems, providing safe login from any location or device.

Another feature that we find interesting is the audit logs and reporting, which has helped us track who, where, and how users logged into the system.

Using OneLogin by One Identity has positively impacted our organization. We are able to comply with client compliance requirements and have managed to reduce takeover time risk. Even if a password is stolen, an attacker cannot log in without second-factor authentication, making it more secure.

Since we started using OneLogin by One Identity, we have noticed a decrease in security events, stolen passwords, and non-compliance adherence issues.

It should also include device posture checks and provide risk scoring.

We decided to switch from Okta to OneLogin by One Identity because Okta required heavy on-premises maintenance and frequent patching and had limited MFA options. We could not create adaptive policies, which was the main reason for our switch. OneLogin provides cloud-native SSO, automated provisioning, stronger MFA, and easier multi-tenant management, making it more efficient for an IT-based service company like ours.

Regarding pricing, I do not know much, but I have heard from our sales team that the licensing for OneLogin by One Identity is moderate compared to other vendors.

My advice to others looking into using OneLogin by One Identity is that they should proceed with it. It is cost-efficient and provides more features for the cost compared to other vendors available in the market. It reduces our time to go live, and we have not made any changes to our existing network. OneLogin's heterogeneous support for various security vendors is excellent, and we can reduce our IT support security tickets. I would advise peers planning to purchase this solution to proceed without hesitation. I would rate this product an eight out of ten.

My main use case for OneLogin by One Identity involves single sign-on, multifactor authorization, and role-based access.

For example, we have an email platform called DID Mail where we use single sign-on from OneLogin by One Identity to authenticate our users and use that same authentication on our different platforms such as virtual info and different mail platforms.

The important thing we use about OneLogin by One Identity is role-based access, where our employees sign up and can see a different interface on the same platform according to their roles.

In my opinion, the best feature OneLogin by One Identity offers is the single sign-on feature, which works seamlessly while integrating with any languages, allowing our developers to integrate with most of our platforms easily.

Security is a good aspect of OneLogin by One Identity, and our user experience is also good and mostly positive.

OneLogin by One Identity has positively impacted our organization by improving our user experience. The user experience has improved as it has saved us time, especially because the session-based login is beneficial. A user logs in for the first time and does not have to log in every single time.

OneLogin by One Identity can be improved by implementing good user interfaces or different kinds of user interfaces, which might help our users navigate much faster.

They can mainly improve their support, as they have a high response time. Decreasing it would be beneficial.

I have been using OneLogin by One Identity for about five to eight months.

OneLogin by One Identity is mostly stable.

OneLogin by One Identity's scalability is mainly automatic, so we do not have to do much. We just contact the vendor to inform them about our number of users if it increases drastically.

Our developers typically handle the integration process with the help of the support team, which is very fast and they get assistance whenever they face challenges.

Customer support is fast, but they sometimes have a high response time, such as five to ten hours, which can be problematic.

Previously, I used CyberArk Identity, and we switched because of the pricing. The main reason for switching was the pricing and the complexity of their admin user interface.

We have seen a return on investment as we have saved a lot of money, approximately ten to twelve percent, compared to our earlier use of a different identity platform such as CyberArk, which was costly.

My experience with pricing, setup cost, and licensing is good, but it sometimes gets expensive when the number of users increases.

Before choosing OneLogin by One Identity, we evaluated other options including Okta and different platforms, but we found that OneLogin by One Identity is overall better than Okta.

My advice to others looking into using OneLogin by One Identity is that if you need better security, user interface, and a faster user experience, it is the way to go, although the support system lacks at times.

They can improve their support and reduce the price. I would rate this product an eight 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.

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.

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.

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.

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.