I’m planning to migrate the Connect app to Forge app. The connect application has some user data stored under the clientKey provided in the installation event. I was trying to use current connect app rest endpoint as a remote Forge endpoint. I’ve implemented new authentication code to verify the FIT token and extract the data in this token. Unfortunately none of the field in the FIT token matches clientKey from the Connect app. How can I match the old clientKey with the FIT token to know which client sends the request ?
Similar to some other threads on here what you want to do is map the client key in the lifecycle payload with the installation ID that comes in the lifecycle payload when each app installation moves from connect to forge: Cloud ID in Connect lifecycle HTTP request payload
If you are using one of the atlassian connect frameworks then we’ve done this for you. If you are not, then you can go look through their source code and see how we did it for a very practical example.
Hi @TReb, our team is also working through the connect to forge porting and encountered something similar where we needed the clientKey connection to access connect app properties.
We are using the Node Atlassian connect express package, and the addon.associateConnect() middleware. I don’t know how it works behind the scenes but it was able to take the FIT and return a legacy httpClient based on the clientKey.