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.

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.

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.

We initially began looking at it because we wanted to have a streamlined login process for multiple services, we didn't want to have people with multiple credentials everywhere.

At the time, Microsoft didn't have a very good single sign-on solution; they were using local on-premise servers and I wanted something that was cloud-based. I wanted it to have high availability and be easy to manage.

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 came into the company and they were already using it. I didn't see a need to change. I know Okta is growing alongside OneLogin. However, I haven't really seen a need to change.

Before choosing this product, we also evaluated Okta, Ping, HelloID, Shibboleth, CAS, and Gluu.

Before choosing this product, we also evaluated Okta.

If the customer is already heavy on the Microsoft Windows platform and they have an inclination towards Azure, we compare how Azure would work for the customer versus OneLogin. That is where we make a decision. 

If the client doesn't have much of a directory requirement in the environment, then OneLogin would be a good choice.

Yes – the other options included Ping Identity and Okta.

Currently, upper management is asking that we look at other solutions. We're looking at Okta while we start the process of seeking out other solutions to compare.

Not as in depth as we did with OneLogin.