-
-
Notifications
You must be signed in to change notification settings - Fork 266
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.
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
Identity Server Tenant Id Mismatch on password update #868
Comments
Hm, I suspect that the password reset code path somewhere calls |
Hi Andrew, Thanks for getting back to me very quickly. I start the SQL trace the moment before the "PasswordReset" page is loaded. If the find method was called, I would expect to see some sort of query against the identity database without a tenant id global filter? The error occurs when save changes in MultiTenantIdentityDbContext is called. |
Hi Jaime, question, is your Identity model customized at all beyond just inheriting from the multitenant identity db context? What is in the method you call inside |
Andrew, I have configurations for all the identity tables. The identity user has a couple of extra columns along with a non clustered index on the tenant id column that gets created automatically by Finbuckle.
The remaining tables just create a non clustered index on the tenant id column in their respective configurations
Other areas work fine without any issues such as registration, login and logout. |
I am trying to update a users password, but keep getting a tenant id mismatch error thrown in Finbuckle
Reset password page
The error occurs when the user manager calls the method ResetPasswordAsync.
Error captured in Seq shows the user manager is failing on UpdateAsync
I have setup my IdentityDbContext so that it inherits from MultiTenantIdentityDbContext.
The data currently in the aspnet users table has two users in each tenant. The highlighted users have the same email address but are in different tenants
Here is my tenant table, which resides in a seperate API. All other APIs do tenant resolution to redis cache, if the tenant is not found, it goes to the http store. These are the two tenants in the table and the tenant that I am using is highlighted.
I ran a SQL profiler to see why there could possible be a tenant id mismatch. There are 2 statements that execute just prior to the exception and appear to be getting data belonging to the correct tenant identifier '1B8E302B-B931-4CAE-B404-A42B7D1E8895' and tenant id 'CE760000-58B6-2C33-7E0D-08DC8BE9C022'.
Do you have any idea why I am getting a tenant id mismatch? If you need more information let me know
The text was updated successfully, but these errors were encountered: