Activities of "maliming"

but that didn't work out.

Can you explains why it doesn't work?

hi

You can try to add it in HttpApi.Host.

hi

You can add a special column for IdenttiyUser, change it after logging in, and check it in the logged-in request.

You're welcome.

The only way to make it work, it is to add the reference of Blogging.Application.Contracts.Shared to my domain project, which will make the architecture not clean again...

Hi

Maybe you can reference of Blogging.Application.Contracts.Shared to DbMigrator. then move your IDataSeedContributor to DbMigrator project.

hi

https://github.com/IdentityServer/IdentityServer4/issues/4535 https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-5.0

hi

I think this limitation has nothing to do with CORS, it is a browser limitation.

Did you changed the TenantKey ?

services.Configure<AbpAspNetCoreMultiTenancyOptions>(options =>
{
    options.TenantKey = "__tenantId";
});

hi BassaSolutions

Can you share a simple project? liming.ma@volosoft.com

hi

Can you try to add the AbpAccountClaimsPrincipalFactory?

https://github.com/abpframework/abp/issues/8888#issuecomment-833167705