CODEWITHSUNDEEP
asp.net-coreasp.net-identity
Mark
Mark

Reputation: 357

CreateAsync doesn't save IdentityUser to database with derived IdentityUser

When Posting the following code works fine until it reaches the _userManager.CreateAsync method. No data is saved to the database.

[Route("api/[controller]")]
[ApiController]
public class ValuesController : ControllerBase
{
    private readonly ApplicationDbContext _appDbContext;

    private readonly UserManager<IdentityUser> _userManager;

    public ValuesController(UserManager<IdentityUser> userManager, ApplicationDbContext appDbContext)
    {
        _userManager = userManager;
        _appDbContext = appDbContext;
    }

    [HttpPost]
    public async Task<IActionResult> Post()
    {
        if (!ModelState.IsValid)
        {
            return BadRequest(ModelState);
        }

        AppUser user = new AppUser();
        user.Email = "[email protected]";
        user.FirstName = "mark";
        user.LastName = "Macneill";
        user.UserName = "Saints22";
        await _userManager.CreateAsync(user, "P4$$word");

        return new OkObjectResult("Account created");

    }

    [HttpGet]
    public ActionResult<IEnumerable<string>> Get()
    {
        return new string[] { "value1", "value2" };
    }
}

Upvotes: 1

Views: 1146

Answers (3)

neggenbe
neggenbe

Reputation: 1885

I came across a similar issue and found out that the issue was because of the password restrictions:

var result = await userManager.CreateAsync(user, password);

result.Succeeded turned out to be false.

To manage password restrictions you can update the policies as follows in Program.cs:

builder.Services.AddIdentity<AppUser, AppRole>(options => {
    // ---- customize your settings here...
    options.Password.RequireDigit = false;
    options.Password.RequiredLength = 6;
    options.Password.RequireNonAlphanumeric = false;
    options.Password.RequireUppercase = false;
    options.Password.RequireLowercase = false;
    options.SignIn.RequireConfirmedEmail = true;
    options.SignIn.RequireConfirmedAccount = true;
    // many different options to setup here!!!
});

Upvotes: 0

Neville Nazerane
Neville Nazerane

Reputation: 7019

You don't seem to be using the IdentityUser directly but instead a AppUser class. This might be a class extending IdentityUser<> or IdentityUser. I am not sure if you have the rest of your setup right, so here is the process:

If you have created a custom AppUser class, let's say you created it as follows:

class AppUser : IdentityUser<int>

This would mean you have assigned the primary key as in int. However, if you extended IdentityUser instead, note that IdentityUser extends IdentityUser<string>, meaning your key is a string. Going ahead I am going to assume your key is int. If not, you can make the changes accordingly (change all ints to your key type.

In your startup class, you need to be adding the following to register this as your user class used for Identity

services.AddIdentity<AppUser, IdentityRole<int>>()
        .AddEntityFrameworkStores<ApplicationDbContext>();

Your ApplicationDbContext needs to be defined as follows:

public class ApplicationDbContext : IdentityDbContext<AppUser, IdentityRole<int>, int>

If you don't want to use IdentityRole<int> in the above two pieces of code, you can define a custom role class as follows:

public AppUserRole : IdentityRole<int>

Once you have these setup, you need to inject UserManager<AppUser> not UserManager<IdentityUser>.

Upvotes: 2

Mark
Mark

Reputation: 357

Thank you neville-nazerane

I had IdentityUser in dependency injection and all I had to do was change IdentityUser to AppUser.

Startup.cs

services.AddIdentity<AppUser, IdentityRole>()
    .AddEntityFrameworkStores<ApplicationDbContext>()
    .AddDefaultTokenProviders();

Upvotes: 0

Related Questions