We were not using any other solution.

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.

Prior to OneLogin, we used AD FS.

One problem with AD FS is that it's very costly. We had to spin up virtual servers to accommodate it, and it wasn't as flexible in creating new applications with single sign-on.

Also, OneLogin lets you provide other features whereby you can manage all of the applications that aren't single sign-on, and SAML-specific. It's a bit of a different tool. It provides me with all of the things that AD FS produced or utilized, but it added on other features which have helped with single sign-on, multifactor authentication, and access to other password tools.

We use several tools including LastPass and Microsoft Azure Single Sign On.

The reason that we use LastPass is that it allows us to share passwords with external users. We use Microsoft Azure for some services because it's more of an automated stream and flow, for the way that our Active Directory is set up.

We have multiple tools but OneLogin is our primary one.

I did not use a different solution previously. I have used Okta elsewhere and I like it. I've used AD as well back in the day, however, OneLogin and Okta are a step ahead.

We transitioned from a different provider. The previous provider went out of business.

We did not previously use a different solution.

We have used other solutions in different places. For cloud solutions, we have used Microsoft Azure and Oracle Cloud Services, their Cloud Identity Services. We recommend this solution based on our client's needs. 

There was no SSO solution with cloud based SAAS services before OneLogin was chosen.

We have tried Okta, and currently, we are trying to go through the company's product manuals. We're working to purchase a subscription on a monthly basis for 5 or 6 users. We are still exploring what the pros and cons are to see if it will fit with our requirements. 

Both products are great. Okta does provide user management so I can have all my users' applications in a single location. With OneLogin, I need to indicate the application and supply the technical application via a plugin. We need to have the plugin for OneLogin which we don't need with Okta.

An internally developed solution. We switched because of contractual security obligations to our clients and opted to let a third party that had already invented the wheel do it for us.