Adding IdentityUserClaim navigation property to ApplicationUser causes migration to create new FK

[mohaaron]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I am following the directions for adding a navigation property from ApplicationUser to IdentityUserClaims and keep getting a migration from it that is not empty as these directions state it should be. Am I doing something wrong that's causing changes to the migration?

https://learn.microsoft.com/en-us/aspnet/core/security/authentication/customize-identity-model?view=aspnetcore-8.0#add-navigation-properties

When I add the Claims navigation property to ApplicationUser the migration creates the following.

public class ApplicationUser : IdentityUser
{
    public required string FirstName { get; set; }
    public required string LastName { get; set; }

    public ICollection<IdentityUserClaim<string>> Claims { get; set; } = new List<IdentityUserClaim<string>>();
}

protected override void Up(MigrationBuilder migrationBuilder)
{
    migrationBuilder.AddColumn<string>(
        name: "ApplicationUserId",
        table: "AspNetUserClaims",
        type: "TEXT",
        nullable: true);

    migrationBuilder.CreateIndex(
        name: "IX_AspNetUserClaims_ApplicationUserId",
        table: "AspNetUserClaims",
        column: "ApplicationUserId");

    migrationBuilder.AddForeignKey(
        name: "FK_AspNetUserClaims_AspNetUsers_ApplicationUserId",
        table: "AspNetUserClaims",
        column: "ApplicationUserId",
        principalTable: "AspNetUsers",
        principalColumn: "Id");
}

I have also tried adding the following configuration for ApplicationUser but it makes no difference.

public partial class ApplicationUserConfiguration : IEntityTypeConfiguration<ApplicationUser>
{
    public void Configure(EntityTypeBuilder<ApplicationUser> builder)
    {
        builder.Property(p => p.AccountOwnerId);

        builder.HasMany(e => e.Claims)
                .WithOne()
                .HasForeignKey(uc => uc.UserId)
                .IsRequired();
    }
}

Expected Behavior

The migration created after adding the Claims navigation property is empty as stated in the directions.

Steps To Reproduce

Here is a sample where I have reproduced the problem.
https://github.com/mohaaron/AddClaimsNavigationToAppUserBug

Exceptions (if any)

No response

.NET Version

8.07

Anything else?

No response

[mkArtakMSFT]

Thanks for contacting us. It looks like the problem is that you have commented out the relationship expressing code here:
https://github.com/mohaaron/AddClaimsNavigationToAppUserBug/blob/6095ad5b69e5ef528fbc13b69f0f5cc618bd7ccf/AddClaimsNavigationToAppUserBug/Program.cs#L38-L43

By not having that code during the first migration you basically state that you won't have such a relationship (the FK). The bottom line is that you have to add the Claims property and that code at the same time before generating the migration.

[mohaaron]

@mkArtakMSFT I've tried this multiple times and still get the same issue. I've pushed up the changes with a new migration where you can see that it's still trying to create a new column with the name ApplicationUserId on the Claims table

[mohaaron]

I've also tried deleting the migrations and creating an initial migration with the ApplicationUser.Claims navigation property and the relationship included. I get the following table definition.

migrationBuilder.CreateTable(
    name: "AspNetUserClaims",
    columns: table => new
    {
        Id = table.Column<int>(type: "INTEGER", nullable: false)
            .Annotation("Sqlite:Autoincrement", true),
        UserId = table.Column<string>(type: "TEXT", nullable: false),
        ClaimType = table.Column<string>(type: "TEXT", nullable: true),
        ClaimValue = table.Column<string>(type: "TEXT", nullable: true),
        ApplicationUserId = table.Column<string>(type: "TEXT", nullable: true)
    },
    constraints: table =>
    {
        table.PrimaryKey("PK_AspNetUserClaims", x => x.Id);
        table.ForeignKey(
            name: "FK_AspNetUserClaims_AspNetUsers_ApplicationUserId",
            column: x => x.ApplicationUserId,
            principalTable: "AspNetUsers",
            principalColumn: "Id");
        table.ForeignKey(
            name: "FK_AspNetUserClaims_AspNetUsers_UserId",
            column: x => x.UserId,
            principalTable: "AspNetUsers",
            principalColumn: "Id",
            onDelete: ReferentialAction.Cascade);
    });