closing this ticket. will be fixed in the next release if you encounter the same problem you can reopen this.
the hacky way is disabling IMultiTenant data filter to access data btw different tenants. see https://docs.abp.io/en/abp/4.4/Data-Filtering#imultitenant
but this is possible if all your tenants share the same DB.
if you change the tenant explained in the following doc, ABP Framework will set the TenantId https://docs.abp.io/en/abp/4.4/Multi-Tenancy#change-the-current-tenant
ConfigureIdentityServer()
method.check out the following document for this scenario: https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Migrations#using-multiple-databases
seems like a problem related to Visual Studio.
this package doesn't belong to the ABP Microsoft.VisualStudio.TestPlatform.Fakes
try to run tests via command line
this is not possible in ABP!
if you need such a requirement, it means you are on the wrong path. reconsider why you need a user to be logged in tenants. alternatively, you can create the same user with the same credentials in each tenant. but the architectural design doesn't allow sharing data between tenants, because each tenant must be considered as a different instance (setup) of your application.
The following docs will help you
see https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-app?tabs=dotnet#get-an-access-token-from-azure-ad
see https://docs.abp.io/en/abp/latest/UI/AspNetCore/Customization-User-Interface , https://community.abp.io/articles/how-to-customize-the-login-page-of-an-abp-blazor-application-by4o9yms
See Easy CRM It's based on the open-source template but you can understand the basics of a realworld app. The latest EasyCRM has an issue which will be fixed in the next release. but you can checkout the code