Question posted in
The official documentation can be found here.

Asp.net – Using a custom user model with .NET 8 Identity API Endpoints

I am using the new Identity API endpoints from my ASP.NET Core API project, but I would like to use more custom properties for application user.

My user class looks like this:

public class ApplicationUser : IdentityUser
{
    [StringLength(256)]
    public string? Name { get; set; }
    [StringLength(256)]
    public string? Surname { get; set; }

    /// <summary>
    /// Years and fraction of year of experience on drums
    /// </summary>
    public float Experience { get; set; }
}

Identity configuration:

public static IServiceCollection ConfigureIdentity(this IServiceCollection services, IConfiguration configuration)
{
    var connectionString= configuration.GetConnectionString("IdentityConnection");
    //Guard.Against.Null(connectionString, $"Connection string for 'IdentityConnection' not found");

    services.AddDbContext<AppIdentityDbContext>((sp, options) =>
    {
        options.UseSqlite("DataSource=app.db");
    });

    services.AddScoped<IApplicationDbContext>(provider => provider.GetRequiredService<AppIdentityDbContext>());

    services.AddScoped<AppIdentityDbContextInitializer>();

    services.AddIdentityApiEndpoints<ApplicationUser>()
        .AddRoles<IdentityRole>()
        .AddEntityFrameworkStores<AppIdentityDbContext>();

    services.AddAuthorizationBuilder();
    services.AddTransient<IIdentityService, IdentityService>();

    services.AddAuthorizationBuilder()
        .AddPolicy(Policies.CanAddHomework, policy => policy.RequireRole(Roles.Teacher));

    return services;
}

And in API Program class: app.MapIdentityApi<ApplicationUser>();

Database has been created with custom properties, but while using the register endpoint, I am only able to pass only email and password, no matter what I’ve sent in the request body. I can’t even set the username which is the default property in the IdentityUser class. Always the username is email.

Is there an option to configure the register endpoint to accept a custom body or do I need to get rid of the Identity API endpoints and implement authentication with the old Identity?

Tags:

2

Answers


  1. 0

    The Identity API endpoints provided by ASP.NET Core Identity are designed to be flexible and allow you to edit stuff, but they do have certain constraints, especially when it comes to the signup process. By default, the registration endpoint expects a username and password, and this behavior is deeply ingrained in the way the identity system works. You might need to implement your own registration logic to work on custom properties. Here’s a basic outline of how you could approach this:

    1. Create a class that represents the data you want to accept in the
      registration request.

      public class RegistrationDto
{
    public string Email { get; set; }
    public string Password { get; set; }
    public string Name { get; set; }
    public string Surname { get; set; }
    public float Experience { get; set; }
}

    2. Create a new endpoint or modify the existing one to handle the
      registration logic.

          [ApiController]
    [Route("api/account")]
    public class AccountController : ControllerBase
    {
        private readonly UserManager _userManager; 
        public AccountController(UserManager userManager)
        {
            _userManager = userManager;
        }
        [HttpPost("register")]
        public async Task Register([FromBody] RegistrationDto model)
        {
            if (!ModelState.IsValid)
            {
                return BadRequest(ModelState);
            }
            var user = new ApplicationUser
            {
                UserName = model.Email,
                Email = model.Email,
                Name = model.Name,
                Surname = model.Surname,
                Experience = model.Experience
            };
            var result = await _userManager.CreateAsync(user, model.Password);
            if (result.Succeeded)
            {
                // Additional logic if registration is successful
                return Ok(new { Message = "Registration successful." });
            }
            // Registration failed
            return BadRequest(new { Message = "Registration failed.", Errors = result.Errors });
        }
    }

    3. Ensure that your application’s services are configured correctly.
      You may need to modify the registration process in your Startup.cs
      file.

          services.AddIdentity()
        .AddEntityFrameworkStores()
        .AddDefaultTokenProviders();
    services.Configure(options =>
    {
        // Configure identity options as needed
    });
    // Other service configurations...

    4. If you’re using a client application to register users, update the
      registration request to include the additional properties.

          {
        "email": "[email protected]",
        "password": "myP@s5w0rd",
        "name": "George",
        "surname": "Smyrlis",
        "experience": 6.5
    }

    Thats a basic example I can imagine that can help you over.

    Login or Signup to reply.
  2. 0

    i have the same problem but i think still need to make custom endpoints for it

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search