We have used Keycloak for a very long time.

We had developed something like this in-house some six years ago. Over time, we identified that it was a problem for us to chase the requirements and the changes needed to support more modern authentications, like SAML integrations, multifactor authentications, and other advanced security protocols. So we decided to try to find a vendor that would provide this for us.

We previously used a different solution which was an open-source solution that was on-prem. I can't recall the name of that, but it was an open-source tool. One of the main reasons we switched to Auth0 is that supporting an on-prem version required a certain amount of expertise and management and we didn't need to be spending money on that if we were using a software as a service provider.

The other aspect was that on-prem you have to manage the security yourself. By using a software product as a service provider in the cloud, we were able to outsource those security concerns to them. The security was their responsibility and no longer our problem.

We used regular OAuth in conjunction with our own database for people without social accounts. This is much better because everything is wrapped and normalized through one service. It even supports non-OAuth solutions such as Active Directory and LDAP which is good.

We did not use another SSO product before our current PoC began.

I did not previously use a different solution.

We were using a different solution from a cloud provider. We switched because we felt that the solution that we were using was not really well maintained. It was working, and it was stable, but the customer experience wasn't great. The number of features that were released when we were working with that solution was close to zero.

We previously used AWS Cognito but switched because it did not support many functionalities.