Why is Asp.Net Identity IdentityDbContext a Black-Box?
There is a lot of confusion it seems around IdentityDbContext.
There is a lot of confusion it seems around IdentityDbContext.
By default ASP.NET Identity in VS 2015 uses a string as a primary key for AspNet*** tables. I wanted to to use int-typed id’s instead. After some research it turned out that different typed id’s are supported by the framework out of the box. In the answer below I will show what changes to make to achieve that.
How can I get the password of a user in the new ASP.NET Identity system? Or how can I reset without knowing the current one (user forgot password)?
I am looking for a way to disable the user instead of deleting them from the system, this is to keep the data integrity of the related data. But seems ASPNET identity only offers Delete Acccount.
Why is this happening when we make a call to the AccountApiController.Register() method?
I’m relatively new to ASP.Net MVC and try to use the built-in user login functionality now. I’m able to register an user in the registration view. If I try to login with the created user this also works. I’m redirected to the master page.
I’m using Unity successfully for all regular constructor injection such as repositories etc., but I can’t get it working with the ASP.NET Identity classes. The setup is this:
How do we get the current user, within an secure ApiController action, without passing the userName or userId as a parameter?
I have an ASP.NET MVC 5 application. I’m using the standard ASP.NET Identity provider for user and role management. It is important that I’m using the IdentityUser from an own repository project, but this seems ok. I can register, login, edit users, and manage their roles.
I’m looking at the interfaces on the new ASP.NET Identity classes and the database it creates using Entity Framework Code First. I’m using the Visual Studio 2013 RC.