You can check this class as sample of adding custom claims using custom claims principal factory.
Basically, overriding a module means overriding it's service configurations (pre-configurations, configurations, pre-init; post-initialize; whichever you have configured).
You can override but most of the time, you shouldn't need to.
Instead of overriding the whole module, modules should have options that can be configurable from the end application.
So this operation should mark exports as deleted(in ef core state) and after saveChanges operation it should be deleting all exports from db. But nothing happened. (we also check with sql profiler , there wasn't any deletion operation which should be seen ). And as ef core state we also can't see the state change , children entity stayed as unchanged .
Maybe you have some mistakes on fluent api configurations since you are using private field for your collection and it won't be tracked as default.
Apart from tracking, can you try updating your aggregate root after myAggregateRootObj.RemoveExports(); method like _repository.UpdateAsync(myAggregateRootObj)?
Please check https://stackoverflow.com/a/59640437/2594735.
If you don't want to grant authentication at all to a black-listed IP list (or vice versa), you can do it while signing by customizing SignIn Manager at AuthServer. If you want to check the authorization of an IP to reach a resource, you can add policy authorization to the related service.
Can you check api gateway ocelot configuration? Change DownstreamScheme of your product routing to http if you are hosting product service on http.
Can you share the backend logs where you get HTTP 500?
[16:11:31 INF] Start processing HTTP request GET https://localhost:44325/api/identity/users/assignable-roles?api-version=1.0 [16:11:31 INF] Sending HTTP request GET https://localhost:44325/api/identity/users/assignable-roles?api-version=1.0 [16:11:31 INF] Received HTTP response headers after 68.6132ms - 401
I think you are overriding the current principle of the user with azure signalr principle that causes 401. Is it only occurs at Users page or other pages like Identity Server Management etc returns 401 as well?
It seems you want to use Resource Owner Flow. Remove responseType from your environment settings.
https://docs.abp.io/en/abp/latest/UI/Angular/Authorization#resource-owner-password-flow
You can add a role when the external user is created as explained in this answer. So that, external user will start using the application with a default role you set. Othewise, you need to set manually after they first login externally and their user has been created.