Developers use the solution to build log-in and sign-up experiences. Auth0 provides an API key that is integrated with the code. We provide sign-in and sign-up instead of making our sign-up, sign-in, invite-user, and forgot-password. We buy Auth0 and integrate it; they run it on their cloud.
Our initial use case was authentication. We didn't want to implement anything from scratch, so we needed an out-of-the-box solution. That's why we chose Auth0. Right now, it's deployed on-premises for our development environment and on cloud. The cloud provider is AWS. We're in the beginning stages of a project, so only 10 people are currently using this solution in my organization.
We use this solution for authentication and authorization, and we deploy it on cloud. For example, if you log into a particular portal, this platform will help authenticate a valid user. It supports identity federation, FSO and multi-tenancy.
We are building a software as a service platform of products, and we wanted our customers to be able to have the same seamless experience in terms of how they log into our products. We wanted it to be secure, and we didn't want to use our own development resources in building our own solution. We wanted something that is secure and ready at the beginning of our development so that we have a very short time to market. We wanted it to be a very extensible solution and building something on our own wasn't an option for us. We wanted something that was already there. We also wanted a company that is highly committed to delivering state-of-the-art solutions for identity management. It is deployed in the cloud. This is a software as a service. So, our workloads work in the cloud. We are mostly using AWS, but we also have Azure and GCP. We are a multi-cloud company.
Platform Engineer - Linux at a tech services company with 201-500 employees
Real User
2020-07-12T11:48:49Z
Jul 12, 2020
We were evaluating Auth0 as centralized authentication solution for our in-house development. We are searching for the best solution to take care of this because our product development is ongoing, and we want to find just the right fit. Ultimately, we did not choose Auth0.
Security Architect at a construction company with 10,001+ employees
Real User
2019-11-14T06:33:00Z
Nov 14, 2019
I'm a security architect. The product is used by our customers, not by our company people directly, so I expect we would have several thousand people using this solution.
Auth0 is a comprehensive identity management solution that securely authenticates and authorizes users on different platforms and applications. It offers seamless integration, easy configuration, and reliable performance for managing identity and access. Users appreciate its flexibility, scalability, and support for multi-factor authentication.
With robust documentation and excellent customer service, Auth0 enables developers to efficiently implement authentication and authorization...
Developers use the solution to build log-in and sign-up experiences. Auth0 provides an API key that is integrated with the code. We provide sign-in and sign-up instead of making our sign-up, sign-in, invite-user, and forgot-password. We buy Auth0 and integrate it; they run it on their cloud.
We use the tool for Single Sign-On (SSO) feature.
Our initial use case was authentication. We didn't want to implement anything from scratch, so we needed an out-of-the-box solution. That's why we chose Auth0. Right now, it's deployed on-premises for our development environment and on cloud. The cloud provider is AWS. We're in the beginning stages of a project, so only 10 people are currently using this solution in my organization.
We use this solution for authentication and authorization, and we deploy it on cloud. For example, if you log into a particular portal, this platform will help authenticate a valid user. It supports identity federation, FSO and multi-tenancy.
We use it as an authentication platform for our customers.
We are building a software as a service platform of products, and we wanted our customers to be able to have the same seamless experience in terms of how they log into our products. We wanted it to be secure, and we didn't want to use our own development resources in building our own solution. We wanted something that is secure and ready at the beginning of our development so that we have a very short time to market. We wanted it to be a very extensible solution and building something on our own wasn't an option for us. We wanted something that was already there. We also wanted a company that is highly committed to delivering state-of-the-art solutions for identity management. It is deployed in the cloud. This is a software as a service. So, our workloads work in the cloud. We are mostly using AWS, but we also have Azure and GCP. We are a multi-cloud company.
The primary use case of this solution is to authenticate APIs, customer authentication, and business-to-business authentication.
We were evaluating Auth0 as centralized authentication solution for our in-house development. We are searching for the best solution to take care of this because our product development is ongoing, and we want to find just the right fit. Ultimately, we did not choose Auth0.
I'm a security architect. The product is used by our customers, not by our company people directly, so I expect we would have several thousand people using this solution.