Configuring Core ABP Modules to target different backend APIs in an Angular Front end

[taseaford]

We have several different ABP installations for independent apps. The goal is for all of these apps to utilize our single identity server installation to accomplish both authentication and authorization. Similar to the following illustration:

The problem that we're running into is that, if we follow the instructions here, the Permissions Management module in Angular UI A is hitting App A for it's permissions. We really would like to configure it to point directly to the App Team Identity Server Installation. If it were a service, the api could be set in environment.ts and *.service.ts. But it does not appear that abp modules utilize the same pattern.

The module appears to be using the default api, so I tried adjusting the default to point to our identity server and adding separate api configurations for each of the other services. This effectively caused a login loop since App A was no longer part of the authentication chain. Someone also suggested adding an api named 'AbpPermissionManagement' that pointed to the identity server, but this did not seem to have any effect.

We considered creating a new endpoint or overriding the permissions management endpoint in App A so that it becomes a pass through to the identity server, but we would like to avoid having a repetitive service change for every app.

@hikalkan or @maliming, would either of you be able to provide a suggestion? Are you aware of a way to configure Core ABP modules to target separate APIs from an Angular frontend?