IDM Nodes does not send or propagate transactionId tracking when contacting IDM

Bug description

When using IDM nodes and the IDM endpoint is set,. the X-Forgerock-TransactionId is not sent along. The issue is that from the docs "Configuring the Trust Transaction Header System Property" it states that

AM supports the propagation of the transaction ID across the ForgeRock platform, such as from DS or IDM to AM, using the HTTP header X-ForgeRock-TransactionId.

The X-ForgeRock-TransactionId header is automatically set in all outgoing HTTP calls from one ForgeRock product to another

Alternative Keyword: IDM Provisioning nodes does not propagate TransactionId

How to reproduce the issue

1. Create a tree like

2. Next for the Global > IDM Provisioning set things like

3. The above can be a to IDM (or thru a LB to sniiff the traffic)

Expected behaviour

For traffic to IDM, we expect to see payload like

GET /openam/schema/managed/user
Accept-API-Version: protocol=2.1
Accept-Language: en
X-ForgeRock-TransactionId: a4b98e34-484a-46d2-907c-fa91f2eaa943-4195/0
Host: idmhost:8080
Connection: Keep-Alive
User-Agent: Apache-HttpAsyncClient/4.1.4 (Java/11.0.8)

Current behaviour

The is no X-Forgerock-TransactionId

Work around

-

Code analysis

 Does not setup transactionId propagation