Forge remote bearer token for storage API

[ibuchanan]

@JunheokCheon

if FIT(forge invocation token) contains the information about storage of which installation instance of forge app that I want to deal with.

It might but you should not depend upon that data inside the token. The policy of Atlassian regarding tokens is they should be considered opaque:

About the format of Atlassian security tokens

Recently, @GuilhermeBueno and I worked a support case about the OAuth 2.0 authorization code exchange. The first step of the flow in OAuth 2.0 (3LO) apps is retrieving the authorization code by directing the user to the authorization URL. The authorization code is returned as a parameter in the URL. The OAuth 2.0 specification does not specify how that authorization code is formatted or what size it should be. In our case, the reporter noted the authorization code from Atlassian was once return…

@JunheokCheon

And if I have to use invokeRemote() to get FIP underneath request headers because I am sending HTTP request from index.js file (forge platform) to Azure Function(HTTP trigger), not in custom UI script, and I am not seeing authentication request header from azure function side.

I’m not sure I understand. Can you explain your index.js in Forge terms? In other words, where is the JavaScript function that makes the HTTP request referenced in the Forge manifest?