All geek questions in one place

User Registration Process Using IdentityServer4

I would like to use IdentityServer4 for authentication in my ASP.NET Core MVC web application, but the user registration process seems inconvenient. Most websites that require user registration do not redirect you to a separate site (e.g. Facebook, Twitter, etc.) to register if you use local user accounts.

One solution is to host IdentityServer4 in the same process as my MVC client, but this is not recommended.

Are there any good examples of real local users in IdentityServer4?

+4
source share
1 answer

IdentityServer is designed to authenticate existing users, not create new users. In our use case, we have 3 projects that play a role:

  • Authentication server
  • Secure API
  • Supplier Identity Project (aspnet core identity)

Users are created by an API call that creates the appropriate structures in the identity provider. Our authentication server makes calls to the authentication server when checking for token requests. Our API uses an identity server to protect resources and our identity provider to obtain information that we may need regarding this user that are not contained in claims (for example, permissions).

, ( ), Identity Server - . .

EDIT: @peyman : aspnet (http://odetocode.com/blogs/scott/archive/2013/11/25/asp-net-core-identity.aspx).

IUserStore UserManager. , , , . IUserStore - , IdentityServer , IdentityServer . API Policies (https://docs.microsoft.com/en-us/aspnet/core/security/authorization/claims)

+6

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

More articles:


All Articles