Not able to call getDestinationFromDestinationService in multitenant CAP scenario

I am not able to call serviceB from serviceA (both in a provider account) using CAP with multitenancy enabled.

Scenario:
Subscriber Account A -- calls --> ProviderServiceA -- calls (using destination) --> ProviderServiceB.

Internally getDestinationFromDestinationService gets called with the option "alwaysProvider".

The problem here seems to be, that even when "alwaysProvider" is set, the method getDestinationFromDestinationService will still try to fetch a token for the subscriber, using the following information:

• auth endpoint: subscriber auth endpoint (fetched from user token coming from subscriber)
• credentials of destination-service: fetched from provider destination service binding

So it tries to authenticate using the provider destination credentials against the subscriber auth endpoint. This of course does not work and the method fails with an error.

I would expect, if "alwaysProvider" is set, that it does not even try to get a subscriber token first, since this will always fail.

Am I missing something here, or is this maybe a bug?

Start by tracing getDestinationFromDestinationService and its alwaysProvider option in the TypeScript SDK, then reproduce the provider-service-to-provider-service call in the described multitenant scenario. Done means the provider destination credentials are not used against the subscriber auth endpoint when alwaysProvider is set, and the destination call succeeds.