The Okta Identity Cloud

We are using Auth0 as our service provider to allow our enterprise clients to log into their accounts using SSO on our platform. The product and engineering teams have set up our configuration, the solutions and sales engineers set up a SAML connection for each client, and the enterprise support team troubleshoots issues for clients.

We use Auth0 for a few products, both internal and external. It's very easy to set up and use and we've been pretty happy with it overall. Especially since it's very easy to add other providers on top of it with just a few clicks.

We've been able to go from using an external social OAuth provider to five in just a few days--that included removing our integration with that specific social provider and replacing it with Auth0. Once set up, Auth0 makes it super easy to add more providers. Now we have GitHub, Google, Yahoo, Microsoft, and can add more as our customers request.

Our organisation uses Auth0 as our internal identity provider (IDP). Our first use case was customer identity, for teaching in particular. We create and manage all user accounts for staff (tutors) and students.

In the future, we're looking to expand Auth0 to accommodate staff identity and other use cases outside of teaching. This could including general access for non-tutoring staff, membership accounts (which are currently managed by a separate SAAS), and more. This would consolidate Auth0 as our IDP across the board, which it's well-positioned to do so based on early indications. We would also look to benefit from some of the integrations with third parties, to easily federate with SAAS services and simplify access management for our staff.

We implemented support to store and validate a customer's identity using Auth0 for multiple e-commerce websites.
We implemented wrapper support to interact with the Auth0 APIs to fetch, update user information, and also verify the user's identity during login. Currently, we have 10 Auth0 tenants configured on our client's Auth0 account. The community support was commendable during the initial phase of the implementation. As it was not quite straightforward, we faced a lot of doubts that were very well resolved by the community members.

But the community support is very active, and the issues are mostly resolved soon.

We use Auth0 for several of our clients. We develop customer and employee portals for small companies/departments to allow them to manage sensitive data and access secured functionality.

We use Auth0 as an SSO solution across many web sites. It integrates well with multiple web servers and platforms. Auth0 has been much easier to use than other similar systems for both our programmers and our users. We hope to expand our use of Auth0 in the future as well.

We are using auth0 as a single sign on for our multiple SaaS products.

Currently using only Google from Social Provider, since we have technical issues for customization with other providers and Auth0 was not that helpful. Customizing Auth0 requires enterprise-level plan which our budget won't allow, that's why we are using Auth0 only for Google provider.

Auth0 was implemented as part of a public facing SPA we were building as a trial of a new service.
Unfortunately, the project was paused indefinitely before it could be completed due to a shift of priorities, but the Auth0 implementation was incredibly easy and relieved us of a lot of headache that would come with handling authentication and authorization ourselves.
Their documentation is extensive, detailed, and easy to understand, implementation can be done in hours (for more experienced users, maybe even minutes), and the service is rock-steady stable.
I would never not recommend Auth0 to a friend or colleague setting up a new app or service.

Auth0 was used for a project for managing the login, permissions, and security. We wanted an easy and secure way of implementing login with different accounts associated, like social networks. Auth0 facilitates this and more, with JWT Tokens and permissions the security grown more than 2 layers. It also provides a great interface (web page) to manage all users.

[Auth0 is used] as a 3rd party authorization service for students, faculty and hospital administrators.

We are using Auth0 as IAM [Identity and Access Management] as well as RBAC [Role Based Access Control]. Here we are implementing solution for our SAAS which will provide support for multiple client and using Auth0 we will do IAM and RBAC.

We have a mature product with a lot of users in an existing username / password login system. Auth0 made migrating that to SSO and social authentication easy. This is a big win for us for several reasons<br><ol><li>We're in the process of redesigning our entire UI. We want our customers to have the smoothest transition possible so we're keeping both the old and new versions online at the same time.</li><li>Our users can login with a federated identity (Google, Microsoft, Twitter, etc) with no extra work on our part</li><li>We're working on two new offshoots of our main product. With Auth0 and SSO we'll be able to easily keep our users logged in across all our products!</li></ol>

Auth0 is being used for the authentication process. There are several websites and applications that need a ready-to-use authentication platform and Auth0 was selected. It's better to let experts managed the authentication process and our clients can focus on the business logic, this way they don't lose time on something already made.

Auth0 manages authentication and authorization for the product we are implementing for one of the biggest name in content management industry. We need not to worry about users authentication and authorization process as Auth0 provides with high level of security.
Implementation is very simple, scalable, reliable and secure. Developer can easily learn and implement as documentation is proper and helpful.

We use Auth0 for staff and admin users to manage our SPACE product. It gives us secure auth and IAM to the front and backend of our application so that our people can truly Work From Anywhere.

[Auth0] handles all the configuration and integration to out external MDM systems. Saves a lot of time configuring and maintaining data about data that is not essential to business needs.

We use [Auth0] as the authentication to an internal cloud management platform. It allows us to outsource authentication securely to experts while we focus on delivering out cloud functionality

OKTA Identity cloud is being used in our organisation for configuring SSO for SAAS applications, On - perm application and applications in our own data centre. We are using OKTA Identity system to manage the users in the directory which is the internal directory for our organisation. OKTA is being used for configuring Multi factor authentication to make sure the users who are from our org is using the applications.

We are using OKTA in our Organization as part of SSO and MFA for users in some application login and Citrix currently. We are planning to implement OKTA in the entire organization by 2021 Q1. As our org is planning to move to the cloud, OKTA is the best solution for us as it currently suits our org, provides unlimited user onboarding, and easy for application implementation either inbuild or custom.

We use The Okta Identity Cloud as an organization. It addresses the consolidation of various accounts into one. Employees love the SSO feature and having to memorize fewer passwords. This also helps reduce the amount of password resets we have to do across different platforms, resulting in more time to handle other issues.

We worked with a government agency interested in a FedRAMP-approved, single-sign-on solution that supported native smart card authentication. Another requirement was the ability to authenticate users from outside the government agency in the same tool. After looking at various solutions that usually required an on-premises appliance to support smart cards, we decided to move forward with Okta Identity Cloud.

We use Okta Identity Cloud to be the cloud-based brokerage, so it is the backbone of the business model. Everything is in the Cloud--everything is digital and accessible and everything is secure. We have the ability to onboard digitally without the primary staff being bogged down by repetitive functions. We can collaborate across the country and around the world.

Okta is being used across the organization as a central identity provider for internal services that support it. We mainly use Google/GSuite as the identity provider for our business applications, but Okta is used to broker access to GSuite. It is integrated with a range of business and internal development/monitoring tools we have.

Okta Identity Cloud is used as the single sign-on solution across multiple verticals at our organization. It has helped to provide various integrations to enable our workforce to seamlessly sign on using multi-factor authentication to various internal portals and tools. We have been able to integrate it in to our Active Directory as well, providing seamless user management through a single set of tools.

Okta Identity Cloud is used as a single sign on for all our enterprise applications. Okta Identity Cloud ensures the application is all secured and can be logged in seamlessly without connecting to each application. It has two-way authentication which is very useful. Okta Identity Cloud is a perfect solution for small, medium, and large organizations.