High Description
The big picture is that outgoing trusted apps is currently broken for Bamboo 3.1 (incoming TA is unaffected).
For Activity Streams 5.0 we have a Bamboo instance applinked with a JIRA, Confluence, and FeCru, and all applinks in this example use trusted apps auth.
We can fetch remote Bamboo content from other products just fine as those products' trusted application data is properly stored (and fetched) in the Bamboo instance.
However, we cannot fetch remote JIRA/Conf/FeCru data from Bamboo as this causes a lookup in the other products' trusted apps implementations for the Bamboo TA at which point its looking for the wrong application id.
Within the applinks config servlet, if I disable trusted apps auth (which deletes the TA entry) and then re-enable it (which creates the TA entry) then everything works great, we can fetch remote content again. But once I restart Bamboo, its back to square one and Bamboo can't fetch remote content.
Also, if I switch to using basic auth for example, everything works fine.
An example failing request contains the following headers:
X-Seraph-Trusted-App-Status ERROR
X-Seraph-Trusted-App-Error APP_UNKNOWN; Unknown Application: {0}; ["C0A80F9A013090143F854DB93770C704"]
(while debugging into JIRA I saw that, at the time, JIRA had my Bamboo recognized as a trusted app but with the app id "7F000101012C3CBF8829BE8F0B14DE02")
and an example successful request contains the following headers:
X-Seraph-Trusted-App-Status OK X-Seraph-LoginReason OK