License a Forge app migrated from Connect

Forge Adopting Forge from Connect
,
1

Hi,

I’m migrating a Jira app from Connect to Forge following the instructions at

and generated the manifest.yml (from the Connect app descriptor) that specifies the Connect app as “remote.”

The Forge app only consists of the manifest.yml file; it has no additional code.

Both the Connect descriptor and the Forge manifest have consistent licenses:

I’ve verified that if I had the Connect app installed and licensed in a Jira instance, and I update it with the Forge app… everything works correctly.

But if I directly install the Forge app on a Jira instance, I get an error about the app not being licensed. This is to be expected, since the app that actually needs the license is the Connect app.

My question is, when the Forge app is in production, how will users be able to obtain licenses for the Forge app if the app must be licensed is the Connect app? Should the Forge app be extended beyond what is indicated in the migration tutorial and add code to verify licenses?

Thank you very much.

1 Like
2

Hi @dortiz,
The Forge app will use the same licensing data as its Connect predecessor. You can find information about how to test various license states and how to check the license state in the Forge parts of your app here. It does work a little differently, for example Marketplace access tokens don’t work.

3

Hi @jhazelwood,

thanks for your reply.

My question stems from exactly what you’re saying.

Let me explain in detail:

As I mentioned, I migrated my Connect app to Forge. The Forge app only consists of the manifest.yml file, which includes the Connect app as “remotes”

Now I have two scenarios:

  • Scenario 1: If I had the licensed Connect app installed in a Jira instance, and I update it with the Forge app… everything works.

  • Scenario 2: If I install the Forge app in a clean Jira instance (without the Connect app installed), it doesn’t recognize the license.

image
image722×179 3.47 KB

I’ve tried two ways:

  1. The old version: using an environment variable.
forge variables set -e development LICENSE_OVERRIDE active
  1. Installing with the license enabled.
forge install --environment development --license active

I’m also not sure if it could be an issue with the Forge environment, because I had a similar experience with storage in another Forge app.

Hence my question:
when the Forge app replaces the Connect app in the Marketplace, will users who didn’t previously have the Connect app licensed and install the Forge app be able to use it without licensing issues? Will the Forge license be used to access the Connect app “remotes”?

Thank you very much.

4

when the Forge app replaces the Connect app in the Marketplace, will users who didn’t previously have the Connect app licensed and install the Forge app be able to use it without licensing issues?

Yes, but when you did the following it should’ve set the license to active in both the Connect and Forge contexts:

forge install --environment development --license active

I’m not sure why that isn’t working for you - you might like to raise an ECOHELP to seek further assistance.

5

ok, thanks for your help.