asp.net - Using a Web API Service as Central Authentication Point -


i'm new identity management world, please spare me. :)

what do, have multiple client (mvc) applications talk single web api application authenticate users against. in web api application, use asp.net identity talk database users.

that way, use sso client applications (i guess).

does make sense? me on way implement (links welcome of course)? don't know if identityserver me want?

and side question: when implement way to, how deal same-origin policy?

thank help. :)

i did research myself during last few months , learnt lot identity management stuff. many of guys identityserver (and other projects).

what did following (very briefly):

  • identityserver used provider client applications. cookie , oidc middleware used.
  • i used asp.net identity user service store users in sql server database. (the identityserver configuration way stored in database.)
  • i set web api service uses asp.net identity user manager user configuration (change password, create new users, ...). uses bearer authentication application identityserver provider.
  • as side note, identitymanager used internal admin tool manage users.

if looking setting / identity management system (and thinks can help): please ask. ;)


Comments

Popular posts from this blog

How to run C# code using mono without Xamarin in Android? -

c# - SharpSsh Command Execution -

python - Specify path of savefig with pylab or matplotlib -