Activities of "liangshiwei"

Hi,

Unfortunately we will not be supporting commercial Duende IDS because ABP does not have commercial authorization.

If your company purchase a license for Duende Identity Server, you can get help from Duende Identity Server.

Of course we will also try to help you if we can

Hi,

Of course, you can continue to use IdentityServer.

ABP still maintains IdentityServer, it's just that it's no longer a preferred option for application templates https://github.com/abpframework/abp/tree/dev/modules/identityserver

Hi,

Of course, it already exists, you can use it directly.

For example:

Also, Is there anyway, I can manage Tenant roles where I as a host create delete and update, however Tenant only able to see pre seeded/created roles?

You can set role create, delete, and edit permissions to only apply to the host.

And create a new manage tenant roles page for the host:

public class CreateTenantRoleInput
{
    public string TenantName {get; set;}
    
    ....
}
public class ManageTenantRolesAppService:...
{
     public async Task CreateAsync(CreateTenantRoleInput input)
     {
           var tenant = await _tenantStore.FindAsync(input.Tenant);
           
           using(currentTenant.Change(tenant.Id))
           {
                _roleRepositpry.InsertAsync(..);
           }
     }
}

Hi,

ABP supports multi-tenancy as a first class citizen. You can define multi-tenancy side option while defining a new permission. It gets one of the three values defined below:

Host: The permission is available only for the host side. Tenant: The permission is available only for the tenant side. Both (default): The permission is available both for tenant and host sides.

https://docs.abp.io/en/abp/latest/Authorization#multi-tenancy

You can set the create, edit, and delete permission definitions to host, in this way, the tenant will not have permissions

if access CurrentTenant property, would it get the same value in Method1

I think that's fine, ABP will add the current tenant parameters when sending an internal request

Hi,

Currently communication between microservices uses client credentials: https://docs.abp.io/en/commercial/latest/startup-templates/microservice/synchronous-interservice-communication

We have an internal issue with this, may be available in next version

Hi,

Could you please create a new question? thanks.

Hi,

Will this work for you?

Configure<AbpTenantResolveOptions>(options =>
{
    options.TenantResolvers.Clear();
    options.TenantResolvers.Add(new CustomTenantResolveContributor());
    options.TenantResolvers.Insert(0, new CurrentUserTenantResolveContributor());
});

Hi,

Could share the full error logs?