hi
This is the difference in cookie policies between Safari and Chrome browsers.
You can check this article https://abp.io/community/articles/patch-for-chrome-login-issue-identityserver4-samesite-cookie-problem-weypwp3n
hi
Can you try to change the Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX
package version from 9.0.4
to 4.0.4
?
Thanks.
hi
Please check and share the logs.txt
of your app.
liming.ma@volosoft.com
Thanks
I apologize for this. I'll explain patiently next time. Thanks.
hi
You have a SWMultiTenantConnectionStringResolver
service to output the Current Tenant info
to logs,
if (string.IsNullOrEmpty(_currentTenant.Id.ToString()))
{
_logger.LogCritical($"******* Current Tenant IS NOT resolved *******");
}
else
{
_logger.LogCritical($"******* Current Tenant IS resolved *******");
}
if your entity(eg, UserPermissionView) is not implemented with the IMultiTenant interface, the currentTenant will be null even if there is a tenant claim
This reply is to clarify your output info. To avoid any misunderstanding on your part, that is, the current user has a tenant id
claim, but the current tenant is null
.
Middleware problems are found by debugging your apps.
https://github.com/spospisil/ABP9Integration/commit/9e61bf3a5c2d9444d2c8a37b5250d998d7b3371e
I'm sorry, the project you shared earlier is not the same as your real project. I can only troubleshoot the problem based on the code.
Your problem is that the middleware order is wrong. Nothing to do with IMultiTenant
Please confirm your problem has been fixed with https://github.com/spospisil/ABP9Integration/commit/9e61bf3a5c2d9444d2c8a37b5250d998d7b3371e
hi
Your Blazor will send some api requests to the backend. And an error happened.
hi
I think you can test it with your DB, the page will work.