All geek questions in one place

IdentityServer3 with EF Support and Asp.NEt Identity

I plan to use IdentityServer3 with IdentityServer3.EntityFramework for clients, areas and operational data. And I also want to configure user repository using IdentityServer3.AspNetIdentity

What is the recommendation here? Can I have a single database for clients, areas, operational data, and Identity Asp.Net? Will there be a problem with EF migration if we have ASP.NET identity tables in the same database?

Or do I need to create a seprate database for IdentityServer3.EntityFramework and another for ASP.NET authentication?

I also want to configure users on one client, I'm not sure if this is supported using IdentityServer3

+4
source share
1 answer

, , . , ef datastore . , - , . , , authorize, , " ", . , , OAuth/OIDC. Identity Server, Oauth OIDC.

0

Source: https://habr.com/ru/post/1648039/

More articles:


All Articles