Last post Sep 25, 2017 10:33 AM by AngelinaJolie
Sep 21, 2017 07:09 PM|quarx1911|LINK
Hi, iam a newbie with ASP.Net Core 2.0. I will have in my Web App a custom authentication. I want use my own SQL Database with my own user table. i want use a simple login process .
When i google i found a sample but for Core 1.0. I read that are many things have changed.
Could anyone help me?
Sep 21, 2017 07:15 PM|Dmitry Sikorsky|LINK
Hi! Please take a look at this article: http://sikorsky.pro/en/blog/aspnet-core-custom-user-manager
Sep 25, 2017 10:33 AM|AngelinaJolie|LINK
If you want to custom authentication without Entity Framework, you have to custom storage provider:
and please view the tourist :
The entity Framework is a specific implementation of that that there's identity, which contains all the base interfaces,IUser, all of the interfaces for storing a phone number, for all of your stores, everything behind the scenes, the majority of that
work is stored in Microsoft.AspNet.Identity. The Entity Framework is a specific implementation of that that gives you something out of the box that works with our databases, On the security side, this kind of gives you a little bit of a differentiation,that's
an IUser interface. IdentityUser happens to be, as it stands now, it's an Entity Framework implementation of an IUser interface, so out of the box,you can store things to... So we could find IdentityUser in the EF namespaces. as well, so if you want do any
of your own custom implementation, then you write your own UserStore, but there's one out of the box for you that works.And then we have a RoleStore, which same thing as a UserStore,that's what actually talks to your data provider to in turn talk to your DataStore.
SigninManager.that's just a high-level API to sign a user in. but what if you just want to sign in a user, and that's when you user that inherits from IdentityUser. A UserStore is a specific implementation that talks to Entity Framework.So if you want to
create your own custom implementation, You have to create your own custom UserStore then that uses the appropriate interface.
Video resource :https://channel9.msdn.com/Series/Customizing-ASPNET-Authentication-with-Identity/01