Auth0 vs. Tools4ever UMRA

Auth0 is very well suited for situations where a JSON web token can be used for authorizing APIs, websites, and mobile devices. It's especially useful if the JWT validation can happen at a gateway layer. It's especially useful if you only need to verify the user's email address or mobile number as the passwordless login is easy to implement.

Incentivized

It is very well suited for tying multiple systems and services together, allowing for exchanges of information and account management. I'm not sure of instances that it is not well suited since solution was recommended by folks in education. With that being the case it suited our needs quite well.

• Overall we had very good experience with Auth0. It supports industry standard language or technology for integration. Very good performance.
• It's nice to work with Auth0's APIs and they are flexible.
• The management and configuration dashboard is useful and easy to deal with.

Incentivized

• Imports students and staff into our Active Directory and email system.
• It manages those same accounts, disabling accounts for folks who have left, and creating "Windows" when accounts should be enabled.
• It interacts with our Microsoft AD and our student management software seamlessly. Once accounts are in our AD environment, our student management and other systems create new email accounts automatically for us.

• Auth0 can be somewhat limiting if you want a lot of control over the design of your authentication flow. Custom branding can be done, but it may be limited depending on how you plan to integrate.
• The Auth0 API documentation has proven confusing at times; a single API endpoint's behaviour will change based on inputs and configured settings (e.g. offline_access). Consequently fields that are advertised as being returned in a response might not be there or have different values if you miss a key detail and it can be difficult to debug when this happens. All information required is available in the documentation but requires some digging.
• The toggle to switch tenants feels a bit odd, it works, but I've had a few instances where I didn't realize I was on a staging tenant looking for something that was on the production tenant. Not a big deal, just something to watch out for.

Incentivized

• We have been attempting to get single sign on for students, so they have the ability to change their passwords on their own. The documentation of this process is very dated, and often support isn't even aware that their site issues/ references those older documents.
• During the initial buildup of our server Tools4ever UMRA support was a bit hit and miss, but I will say our ongoing support has been very good.
• Some integration tools had to be custom created.

For our purposes, Auth0 is still one of the best valued RBAC platforms in the market.

Incentivized

- integration and ease of implementation - great over all product support specially for passkey biometric authentication -Auth0 is very reliable to use their API integration for security
verification. It provides best API to integrate our website and application
with Single Sign In option and two step verification option. Sales and technical teams are always there to provide support

Incentivized

There isn't a clear method to get a hold of support when trouble arises if you're on their standard plan. You can file a support ticket and they generally are responsive. I've often been able to find similar questions to the questions I've had when it comes to support in their ticket history, however, some have been closed without a satisfactory conclusion for the original poster.

Incentivized

Auth0 is non-evasive and does not require software download. It is user friendly, seamless, and doesn't require additional actions on the part of the user. IBM Trusteer is none of these things and is based on a technology stack that cannot scale in the same way as Auth0. We believe Auth0 provides a superior solution and is well suited for our own technology stack.

Incentivized

• Development time has been allocated to the more core parts of our business.
• We are confident in the security of our user's accounts and their data.
• Auth0's login flows are customizable which means that we don't have to worry about users being confused when logging in/changing their passwords, and we didn't event have to spend that much time configuring this. (Full in-house development for login could take weeks to get right.)

Incentivized

• We save considerable work hours by a multitude of staff having the system manage and generate accounts for us on a daily basis.
• We have some peace of mind knowing accounts for staff and students who leave our district can no longer gain access to our systems because it automatically disables those accounts.
• Because of the way the system interacts with input that is put in, it automatically creates logical positions which dictate different levels, meaning it automatically sets up when staff gain access and lose access depending on the position they are filling.