Issue #2:
The angular permission check happens locally, the server will check all the permissions of the current user or user's role etc and return to angular.
The menu just checks whether the permission is granted.
hi I will check asap.
hi
Can you add your browser's userAgent in DisallowsSameSiteNone(string userAgent) method?
They does't recognize SameSite=None;
It's should be working.
hi
Can you test your browser via https://samesite-sandbox.glitch.me/ then share the results?
hi Mohammad
I have checked. This is by design.
Your tenant's default connection string should contain the module tables that support multi-tenancy.
The tenant's default connection string means default, So it will no longer look for the connection string on the host side.
If you don't want this behavior, you can customize MultiTenantConnectionStringResolver for some special cases of your.
I have disabled AccessTokenTenantResolver and trying to access the application it still cannot determine the tenant connection string from the database. It only happens when a connection string for a tenant is set in the database.
hi
Can you check the MultiTenantConnectionStringResolver ? I also check it if we remotely.
HI
That's why I need you to confirm the ICurrentTenant .
So your AccessTokenTenantResolver is not working.
The framework has some build in TenantResolver https://docs.abp.io/en/abp/latest/Multi-Tenancy#determining-the-current-tenant
CurrentUserTenantResolveContributor: Gets the tenant id from claims of the current user, if the current user has logged in. This should always be the first contributor for the security.
hi
Can you copy the code of MultiTenantConnectionStringResolver to debug to see what happend?
https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MultiTenancy/Volo/Abp/MultiTenancy/MultiTenantConnectionStringResolver.cs