I'm using ASP.NET Core 1.0 and the identity stuff to authenticate and authorize the users. It all works fine except one single thing:
If the user resets or changes his password, he can't sign-in with the new credentials until the ASP.NET App is restarted. Means the new passwords are successfully saved in the database, but the Method
_signInManager.PasswordSignInAsync() doesn't use the current data, but old one. It seems there is something like a cache in the EF Core or in the SignInManager/UserStore.
Sign-in after registration works also fine, it is just a problem after reset or change of the passwords.
I too discovered a problem with my authentication middleware using a stale DbContext.
One solution was to refresh the user in the auth middleware's identity resolver with the following line of code:
Following this, I was able to verify the user's credentials against up-to-date data.