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 …

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.

1 Like

Topic		Replies	Views
Auth0 as the identity server for a custom database connection Get Help custom-database , custom-login	2	4203	March 2, 2018
Use Auth0 after user authenticated via 3rd party Get Help management-api , users	2	5	April 23, 2025
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	3	5228	March 2, 2018
Use Client Id and Client Secret to Create a JWT for a User Get Help	2	5864	August 29, 2023
SPA for a third party client and domain connection Get Help jwt , auth0 , connections , login , third-party	4	4693	January 22, 2019

Using 3rd party REST API as custom identity provider

Related topics