Cross product access

Forge Forge UI Kit and Custom UI
1

Accessing Jira and Confluence Content with a Single Marketplace App Installation

We currently have an app listed on the Atlassian Marketplace that can be installed in Jira. However, for future releases, we aim to extend our app’s capabilities to also access content from Confluence.

Our plan involves incorporating request functions such as requestJira and requestConfluence. Since this approach involves cross-product integration, we’ve encountered some challenges due to Forge’s current limitation on supporting cross-product access.

Challenges We’re Facing:

  1. Unified Access: We want our app to access both Jira and Confluence content seamlessly.

Current Issue:

Since our app is already listed on the Marketplace, attempting to access Confluence content without a separate installation in confluence results in the following error:

{
  "code": 403,
  "message": "The app is not installed on this instance"
}

TL;DR: Is it possible to extend a Forge app installed in Jira to access Confluence content as well? We’re encountering a 403 error due to cross-product access limitations in Forge.

2

Hello @dnavashola

If you search this forum for all topics tagged with cross-product, you’ll find the answer you seek, such as this thread.

Or refer to the What if my app supports multiple products section of the Listing a Forge app documentation, where it says:

4 Likes
3

As @sunnyape already mentioned:

  1. You need to create two separate apps: one for Confluence and one for Jira. Both apps must be published to the Marketplace.

As a workaround:

  1. The apps can communicate with each other via web triggers. To do this, create a web trigger in the app that “provides” data, which the other app can then access.
  2. The web trigger URL is generated “per instance” and won’t be known until after installation. Therefore, you’ll need a mechanism to inform one app that the other is available at a specific URL.

Important:

  • Web triggers do not use any authentication and can be accessed anonymously.
  • All requests made through the web trigger will be executed “asApp,” meaning they will bypass any user-specific permissions.
3 Likes