What is our primary use case?
We use it primarily as an identity provider. Beyond that, we use the SSO and SAML components. Additionally, we utilize their SmartFactor Authentication to prevent dictionary attacks. This is an additional security measure.
How has it helped my organization?
We needed the solution primarily as an identity provider. We needed something that was cloud-based and not Microsoft-based. We were primarily Mac users and still are to a large degree.
It has helped with compliance and instituted a security measure that isn't very common with other solutions, at least not that I've seen, like putting MFA or second-factor authentication before the password prevents dictionary attacks. Dictionary attacks are when people try to access a given site, whether we SSO or SAML to it or directly to OneLogin itself to gain access to any of the company services. Putting MFA first prevents people or external threat actors from trying to get someone's password and getting access that way. They need that second authentication before they can even type in their passwords.
What is most valuable?
Given that cybersecurity is the client's concern, SmartFactor Authentication has been really handy in checking off some of those boxes.
It's handy that the desktop feature enables users to log in once and have access to all apps and their OneLogin portal. It's useful to have, especially since it’s centralized, since there's MFA protecting it, and since there are various layers of security there. I would say it's impactful. It's something that we needed.
The adoption rate of the solution in our organization is primary. You can't get access to email without going to OneLogin. In that regard, it's a good thing. We need it and we want it. We're essentially enforcing it and everyone has to use it.
The solution provides us with a single pane of glass for access management across our organization. There are some applications outside of it and that's not really OneLogin's fault. They don't offer SSO or SAML.
It's super useful to have a single pane of glass when it comes to access management. It's great to have everything in one place. It's great to have all the logs there in one place. It's easy to see who accesses what. Especially today, there are so many different systems. Keeping everything in one place makes my job easier.
We have not used Smart Hooks to create custom workflows and integrations.
OneLogin work identity helped to free up our time. It seems like the whole onboarding process, offboarding process, and security are easier.
I'm the primary IT guy. We have a third-party consulting firm as well that helps us out, however, anytime I have to onboard or offboard someone, it makes it so much easier.
The solution affected our experience when working remotely. It made COVID pretty much a breeze. We were not impacted at all in any way. We wanted to structure ourselves that way, to begin with. We didn't want to rely on any on-premises technologies in case there were issues. Any of our users can work from anywhere and that's something that we wanted to do from the get-go. We've definitely been able to do that thanks to OneLogin.
The solution helped save money for our organization, either by optimizing time-intensive processes or by increasing productivity.
It’s hard to say, money-wise, however, definitely with time, it’s saved us incalculable amounts of time. Just having a single place to go to onboard or offboard users makes the whole process a whole lot easier. I tend to deploy licenses, at least from Microsoft, automatically from OneLogin for users. I don't have to go into each separate app and create their account there. I don't have to worry about passwords or MFA for any of those services. There are just tremendous amounts of time saved all around.
What needs improvement?
We use the solution SmartFactor Authentication to adjust authentication flows in real-time, depending on the risk score associated with the login attempt. I honestly haven't found that as useful. It's helpful, however, I've run into an issue where it blocks people from signing in. Essentially, if I'm not paying attention to such and such person failed to log in, it doesn't seem like there's an easy way to alert the admin, "Hey, this person was blocked from signing in and cannot sign in at all," even if they're attempting a legitimate sign in. Therefore, while we do utilize it, we keep it at the highest level, just so that if users are traveling, they will not be bothered most of the time by it.
For now, the only thing that needs to improve is the support. I used to have a really good support experience. I'm not sure now that they were acquired by One Identity, it seemed like that changed. It could just be growing pains, however, I feel like their support lately needs some improvement. The product itself works great.
I would like better reporting from SmartFactor Authentication when a user is not able to sign in due to a new location, new IP, new device, et cetera. That would definitely help.
For how long have I used the solution?
As a company, we've used the solution for well over four years, however, I've used it for four years exactly.
What do I think about the stability of the solution?
Lately, I've been a little disappointed with the stability. We had a few outages recently. I don't know if it was two or three. I do know that they went on for hours. The users couldn't SSO into their sites or apps, and that was a bit unexpected, to be honest, one, that we had an outage like that, and two, that it took so long to resolve.
What do I think about the scalability of the solution?
It's highly scalable. We use it pretty much wherever we can. I like that about it. Even though we don't use the desktop product, that has huge potential as well.
How are customer service and support?
I would've given support really high marks earlier. However, it's not as good anymore. I've submitted a couple of cases that kind of helped me, however, the support staff that I spoke with were not super helpful for one of the cases. They never responded and I didn't feel like following up as I just didn't know if I would get the response I wanted or that I was looking for.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
I was part of the initial setup. It's been a while now and it is more straightforward. Initially, I needed to get used to the product and figure out where everything is more than anything. I wouldn't call it that complex. The documentation has been getting better, so that definitely goes a long way. I wouldn't describe the setup as too complex. There's a learning curve, however, it's not super high. For the most part, you can find where things are in the various different menus.
We deployed the solution using two or three IT staff. We're a smaller company.
There are around 45 to 50 end-users. Endpoints were around 75 to 80. We do have a variety of different teams, some of which use different software or different applications. We do have a lot of remote users and it has worked flawlessly for them for the most part work. We've had contractors use it and it has worked flawlessly there also. It's pretty robust and pretty simple to set up new users and give them access to whatever they need.
The solution requires occasional maintenance that is done internally. We look through the logs or look through access.
What about the implementation team?
We did not use an integrator or reseller or consultant for the deployment of the solution.
What was our ROI?
I would say we have seen an ROI, especially in terms of time for IT, time, and security.
What's my experience with pricing, setup cost, and licensing?
The pricing is great and competitive. It's right around where Okta is, and maybe a little cheaper. I
Which other solutions did I evaluate?
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.
What other advice do I have?
We do not use OneLogin desktop feature to extend SSO and Mac OS or Windows machines. I am considering it, however, I know there are also other offerings. We utilize Kandji for Mac MDM and I'm considering trialing that. As far as Windows goes, we have Intune set up and they do SSO. There's no need for a OneLogin client on their desktop. We had that set up before the OneLogin offering, so we just kept to it as is.
We have not used Smart Hooks to create custom workflows and integrations. We use various clouds for our deployment, including Microsoft and Google.
I'd rate the solution overall an eight out of ten. The biggest factor for me from giving it the highest score right now is the support.
The ease of use as far as deploying the users or connecting fast applications is straightforward. Sometimes you do require the help of documentation, however, when you do, the documentation is there and it is thorough. It's a lot more straightforward than something like Active Directory, however, it's not really an apples-to-apples comparison.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.