To support customers in AGC, existing Connect apps need to adopt Forge. To learn more about the adoption process, see this link.
To adapt an existing Connect app, the first step is to convert the Connect descriptor to a Forge manifest.
1 2npx connect-to-forge@latest --type <jira|confluence> --url https://website.com/path/to/descriptor.json
See more detailed steps here.
If you need a sample Connect app, go here.
Follow the steps on how to build Forge apps to deploy and test the Forge app here.
An AGC app should be configured to use the appropriate federal URLs of Atlassian services.
When your app is installed in an AGC tenant, the initial app installation call will be signed with a private key from the key server, for example: https://connect-install-keys.atlassian-us-gov-mod.com. You'll need to use this key server to verify that the installation is correctly signed.
If your app has the ACT_AS_USER scope and you wish to allocate an impersonation authorization token to it, your app will need to request that token from https://oauth-2-authorization-server.services.atlassian-us-gov-mod.com.
Your app’s front end will need to load the Atlassian Connect JavaScript client library from a dedicated CDN at https://connect-alljs-cdn-bifrost.frontend.cdn.atlassian-us-gov-mod.com/assets/all.js.
Our Connect app frameworks allow apps built with them to support AGC with minimal effort.
Such apps will recognize a federal tenant based on its baseURL, which follows the pattern *.atlassian-us-gov-mod.net. The frameworks will use the appropriate federal instances of our services automatically.
If you're using your own approach to building your app, you'll need to use a similar strategy to that used by these frameworks. You can inspect the code for these frameworks to determine the change appropriate to your build. If you currently block install attempts for tenant baseURLs outside of a small acceptable set, you'll need to add the new AGC tenant pattern to that set.
Rate this page: