Skip to content

feat(user): add EformUser.IsActive so a login can be disabled (#971) #972

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
renemadsen merged 1 commit into from
Sep 17, 2026
Merged

feat(user): add EformUser.IsActive so a login can be disabled (#971) #972

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions eFormApi.BasePn/Infrastructure/Database/Entities/EformUser.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,4 +37,14 @@ public class EformUser : IdentityUser<int>
public string EmailSha256 { get; set; }
public string ProfilePicture { get; set; }
public string ProfilePictureSnapshot { get; set; }
/// <summary>
/// False blocks sign-in for this account, a resigned employee say. Not the same as
/// Identity's lockout, which is the automatic brute-force delay.
/// </summary>
Comment on lines +40 to +43
// Keep the "= true". The mapping's HasDefaultValue(true) makes true this property's
// sentinel, and EF Core omits a sentinel-valued column from the INSERT so the store
// default applies. Without the initializer a new EformUser holds false, EF Core writes
// that explicitly, and every account would be created disabled. (That is precisely what
// happens to the shadow property ExternalLoginEnabled today, which cannot have one.)
public bool IsActive { get; set; } = true;
}
Loading