Execute the sql statement directly in the database of your problem.
SET IDENTITY_INSERT yourtable ON
INSERT INTO yourtable (id, name) VALUES (1, 'test 1.0')
SET IDENTITY_INSERT yourtable OFF
I have no verification, but in theory there is no problem. What problem are you having now?
please refer: <a class="postlink" href="https://timmlotter.com/blog/asp-net-identity-invalidate-all-sessions-on-securitystamp-update/">https://timmlotter.com/blog/asp-net-ide ... mp-update/</a>
<a class="postlink" href="https://aspnetzero.com/Documents/Extending-Existing-Entities">https://aspnetzero.com/Documents/Extend ... g-Entities</a>
This tutorial is a step by step guide to learn how to add new properties to existing entities, from database layer to UI layer.
By default, you can access the website. If the website is bound to IP, please bind both IPs.
Can you share the error stack information?
services.ConfigureApplicationCookie(options =>
{
options.Events.OnValidatePrincipal = context =>
{
//You can judge here.
return Task.CompletedTask;
};
});
<a class="postlink" href="https://github.com/aspnet/Security/blob/a0d6d3e88f974ac8b66890b34d2c28ebd3f25de0/src/Microsoft.AspNetCore.Authentication.Cookies/CookieAuthenticationHandler.cs#L178">https://github.com/aspnet/Security/blob ... er.cs#L178</a>
Note: There may be performance issues
I think the problem lies in the asynchronous of foreach. If you haven't solved the email, you can send the project to me (you can streamline the code)
<a href="mailto:[email protected]">[email protected]</a>
If you want to let the user quit immediately, you need to verify the user information for each request (there will be performance issues,).