We’re developing a pretty straight-forward web application (Angular SPA client, .NET Core Web API backend) which will interact (both from the client and from the API) with a 3rd party API (3p-API, for short, in this post). Auth against the 3p-API is done by passing username/passwords to a simple RES…

If you want to pass the username and password from the Auth0 login form to an alternative identity provider you must use a custom database connection. This requires an Enterprise level license agreement to use. [image] Custom Database Connections Learn about authenticating users using …

Thanks for sharing this knowledge on that front @yinzara !

Thank you @yinzara . I’ll be reading up on custom database connections then! Follow-up questions might appear :wink:

Using 3rd party REST API as custom identity provider

Get Help

juliank April 5, 2020, 7:29am 2

Kindly pinging @dan.woda, since you offered your assistance in another thread.

Topic		Replies	Views
Auth0 as the identity server for a custom database connection Get Help custom-database , custom-login	1	4259	April 6, 2017
Use Auth0 session access token to authenticate social connection API Get Help connections , oidc-enterprise-connection	1	838	February 26, 2024
Login with Auth0 using own identity server Get Help login-experience , new-universal-login-experience	1	828	October 3, 2023
Issue access token after third party API validation and include custom claims .NET API Get Help api , authentication , api-authorization , client-metadata , client-credentials-g	2	5286	August 8, 2017
Use Auth0 after user authenticated via 3rd party Get Help management-api , users	1	55	April 23, 2025

Using 3rd party REST API as custom identity provider

Related topics