IdentityLibrary - Reload claims every 30 minutes, check IdentityUser.Enabled

[DavidThielen]

Hi all;

I am using the Identity Library and want to add a couple of things to it. First, I have extended IdentityUser to:

public class ExIdentityUser : IdentityUser
{
        public bool Enabled { get; set; } = true;
}

The additional functionality I want to add is:

1. On login:
   1. If User.Enabled == false, login fails
2. For each user, every 30 minutes:
   1. If User.Enabled == false, user is logged out
   2. User (Principal actually) claims are re-read
3. A method RereadClaims(ExIdentityUser user) that will force a re-read of that user's claims

I think RevalidatingServerAuthenticationStateProvider will do some of this, specifically:

1. It will check if User.Enabled == false every 30 minutes.
2. Is this called on a login? If so, then it handles that issue too.

How can I accomplish the re-read of the claims. I don't need to re-read them myself, I just need to force the re-read. And I do not want to call ForceLogout(), I just want the claims re-read.

And it's fine if I make whatever call and that means that the claims will be re-read the next time the Identity Library checks the cached Principal. It does not have to happen instantly.

For the curious, this is why I want to add this functionality:

1. User.Enabled - Users can be reported in my application. If they are problematic they will be disabled. The disable instead of delete means they can't re-register with their same email.
   1. It's also useful when they are first reported to disable them. Because if we determine they are OK, then we just enaable as opposed to telling them to register again.
2. Re-reading the claims - It's in the documentation, they get an email, and yet... when a user is given a new claim we receive a support request 80% of the time asking why they don't have the new rights. And we have to then tell them log out and back in. Usually when someone gets a new claim, it's a couple of hours or even days before they go to make use of it. So a re-read every 30 minutes will resolve this.
   1. And for the force RereadClaims(), that's so when a user changes their own claims, they have them instantly in effect instead of logging out/in. This is granted rarely needed, mostly for the QA team.

thanks - dave