hi
The Impersonation feature is only available in Blazor Server mode. Blazor WASM does not support it.
https://abp.io/docs/latest/modules/account/impersonation#blazor-wasm
The Blazor WebApp will switch to WASM from servce mode. Then Impersonation displeased.
We will try to make it also work in Blazor WebApp mode.
see https://github.com/abpframework/abp/issues/23729
Thanks.
hi
this problem just appeare in production not in dev
The problem is about JsonSerializerOptions, The JsonSerializerOptions value is different between dev and production.
Can you global search the JsonSerializerOptions keyword in your solution?
Thanks.
hi
Can you grant permissions through the PermissionManager service?
It will manage the cache internally.
Thanks.
Great solution. Thanks 👍
hi
abp get-source <module-name> --version 9.0.0
You can check if the email already exists across all tenants when creating a user.
If your tenant doesn't use a separate connection string, you can disable the multi-tenant filter to perform the query. Otherwise, you'll need to retrieve all tenants and switch to the current tenant before querying.
hi
In this case. You need to verify the user's email/password across all tenants.
The email should be unique among all tenants. Selecting a tenant is not a good choice.
See how to remove tenant selection https://abp.io/support/questions/9755/Hide-Tenant-Selection-in-the-login-screen-MVC#answer-3a1ba8eb-6548-b7f8-8c78-6eda8c4087b0