Activities of "gterdem"

Hi support team, any new on this subject?

ABP design is to use single API resource to single API scope. Because we use permission management for authorization.

If you want to use scope based authorization for your api, just fine.

Can you explain your exact problem? Does IdentityServer Management UI not allowing you to use multiple scopes?

Check your RemoteService configurations under AdministrationService appsettings.

You may have forgotten to override this IdentityService url on pod environment.

I have written a guide about how to use a management module as a microservice; using Audit-Logging as the sample.

Guide should be available today or tomorrow. I will share the guide link.

We've fixed this issue and it will be available in the next patch. However I will keep this issue open until we confirm it is fixed. As a work around, adding appsettings.json and appsettings.secret.json to TestBase projects of related services should fix the issue.

I have reproduced the problem. We'll fix this problem as soon as possible.

Can you share:

1. IdentityServiceEntityFrameworkCoreTestModule ConfigureServices method
2. AdministrationServiceEntityFrameworkCoreTestModule ConfigureServices method

They should be configured as shown above.

Did you manually update your project or used cli to update?

I have no experience nor knowledge about Azure APIM. Token is sent on the header automatically when you start the request from the application. If gateway doesn't manipulate the request headers and just redirects; there shouldn't be any problem.

Ok, can you refer a code or sample if we would like to pass additional headers while redirecting to webapi

You can use aspnet.core middleware by injecting httpContext and add response headers.

Thank you for pointing that out. We will discuss about data filters like ISoftDelete is not being tracked from the parent entity.

I have no experience nor knowledge about Azure APIM. Token is sent on the header automatically when you start the request from the application. If gateway doesn't manipulate the request headers and just redirects; there shouldn't be any problem.

We are planning a new release (5.1.4) on 28.02.2022.

As a workaround, you can update your related MyServiceEntityFrameworkCoreTestModule:

Configure<AbpDbContextOptions>(options =>
{
    options.Configure(abpDbContextConfigurationContext =>
    {
        abpDbContextConfigurationContext.DbContextOptions.UseSqlite(sqliteConnection);
    });
});

to

Configure<AbpDbContextOptions>(options =>
{
    options.Configure<MyDbContext>(abpDbContextConfigurationContext =>
    {
        abpDbContextConfigurationContext.DbContextOptions.UseSqlite(sqliteConnection);
    });
});