How to emulate license?

[SilvreLestang]

Hello,

My Connect app use GET /rest/atlassian-connect/1/addons/{appKey} to check if its license is active.
With a Connect app, we use the private listing feature of the marketplace to generate tokens for each of our dev/PM instances.

But private listing is not available for Forge apps.

How my Forge from Connect app is supposed to “emulate” an enabled license in this case ?

[SilvreLestang]

Same issue for the license object from the URL query string parameters when Atlassian request one of our Connect endpoints, the lic parameter value is none and need it to be active to use my app.

Could you document how we are supposed to do this?

[SeanBourke]

Hey @SilvreLestang,

While an app moving from Connect to Forge can continue to utilise the License API from any Connect modules or remote JWT calls, any Forge modules will not have access to this and would have to evaluate via the license details shared within the app context. I’d recommend watching and voting for FRGE-786 to monitor this.

Forge apps do not currently have an ability to mock license state similar to Connect apps today. I’ve created ECO-242 which you can watch / vote on to share the importance of this capability. With that said, we have supported apps in testing by initially staging rollouts to their own cloud sites, prior to customers being able to update. This provides an opportunity to test and validate your app, prior to existing customers seeing the update option. More than happy to connect and discuss how this works.

Cheers,
Sean

[SilvreLestang]

Hi @SeanBourke,

Thanks for the response and the ECO ticket.

I just want to emphasize that in the current state, we have to modify every piece of Connect code that check/use the license, when “migrated” to Forge from Connect. That makes the migration more complex and difficult.