I’m pleased to announce that the bug fix for FRGE-212 has been released. With this change, the system user provisioned for your app will be given the appropriate permissions tied to the scopes defined in the
permissions.scopes section of your app’s manifest.
Connect on Forge apps
Forge on Connect apps can now access restricted REST APIs using JWT authentication. Connect scopes need to be transformed by appending the scope with
write:connect-confluence ). Refer to Migrate an App from Connect to Forge for more information.
The scopes won’t be synced automatically. There are several actions you can take to ensure the scopes and their associated permissions are being picked up, depending on the current state of your app.
Synching Forge apps with existing scopes
You’ll need to do a major version update (i.e., licensing, scope, or egress endpoints changes). The scope changes will take effect when the sites with your apps have installed the upgrade.
Synching Connect on Forge apps with existing scopes
Due to the changes in how we persist and send lifecycle hooks, we recommend that you do a complete reinstall of your app. Alternatively, if you’re not utilising an uninstall hook then a major version upgrade is sufficient.
New apps, or adding scopes to an existing app
Add the scopes to your manifest and deploy your app. The scopes will be synced with the next installation/upgrade.
Please reply to the thread with any questions or feedback.