Forge app licensing with Paid via Atlassian

Forge
,
1

Hi

Could anyone provide some guidance on how to implement licensing for a Forge App?

Reading the docs here and here
is causing some confusion related the testing and checking of the license.

We want to change from a free app to Paid via Atlassian, which would require a new version and subsequent re-approval.

In order to change the Payment model for an existing app (except for the two situations listed above), you’ll need to release a new version with this change in place.

As per the docs we add licensing: enabled: true to our manifest.yml file.
But it also states:

“Additionally, you should check the license status of your app when your functions are invoked, and implement reduced functionality if your app is unlicensed.”

The app does not offer differing levels of functionality, we just want to bill based on the number of users in the Confluence instance, e.g. 0-10 = free, 11-50 = 0.5c per user etc.

Blockquote In the Atlassian product, the Universal Plugin Manager (UPM) checks the validity of app licenses. The Atlassian product reports the licensing status of the instance to the app in each request. The UPM provides an API that apps use to access the Atlassian licensing system for its license checks.

If we use the Paid via Atlassian payment model, does the UPM handle the licensing checks or how should this be implemented?

Thanks

2

Are you planning to use Forge to implement your app?

Then, enabling licensing does not do anything else than provide a property to your app with the status of the license.

In case eg trial license is expired, your app need to check this and eg disable certain functionality and maybe show an error message, that license is required.

At least, that is how I understood it. :wink:

2 Likes
3

Yes, it is implemented in Forge. I will submit with the change and see what happens. :slight_smile: