Hi @jrichards,
After consulting the AGC developer documentation, I have some doubts how the entire process should look like. Thus, I have a similar question: “Is it enough that…?”
Well, what we have already done (and effectively rolled out to production) is that we’d prepared Email This Issue’s Connect backend to:
- handle lifecycle events received from an AGC site
- obtain OAuth2 tokens from the AGC-specific servers for user impersonation
- load and use the AGC-specific AJS Client library (all.js)
That is, completed all the activities and prerequisites listed in this section.
We also converted our Connect app descriptor to a Forge manifest, resulting in a Connect-on-Forge app. This is currently coming through the app approval review.
So far, so good. On the other hand, what is not entirely clear to me now is whether we have to register and deploy an AGC-compliant Forge app - more precisely, an AGC-compliant Connect-on-Forge app - before moving on to the distribution phase.
If my interpretation is correct, we have to create an AGC variant of our app’s Marketplace listing, i.e. a separate listing for AGC customers.
Unfortunately, it is worded a bit ambiguously, whether a Connect-on-Forge app must be also listed in this way or only native Forge apps must get through the process described here. In other words, shall we create an AGC-compatible Connect-on-Forge app, too, or does it apply to native Forge apps only?
If yes, we’ll have two Connect-on-Forge listings as a result, right? (a standard one and an AGC-compliant one)
As a consequence, we shall not instantly enter the standard Email This Issue’s Connect-on-Forge app details as AGC App ID and AGC App Name in this form (as they must be different also in our case), right?
In my understanding, the recent changes in our Connect backend alone make our app suitable for handling requests from AGC sites. Nevertheless, the app management (AGC-specific Forge Developer Console) and the discoverability on Marketplace still require a Connect-on-Forge app to be transparently listed as an AGC-compatible app.
To do this, we’ll need access to https://id.atlassian-us-gov-mod.com (a kind of AGC-specific Atlassian Admin site?). Will it be possible, as soon as our AGC test site (and the corresponding SAML authentication) is correctly set up? Or do we have to perform further configuration steps, too? Anyway, I cannot navigate to this page at the moment (which might be due to the fact that our AGC site registration is still in-progress).
Sorry, if it all sounds a bit confusing. I hope you can deduce from it where we have uncertainties.
Thanks for your support in advance,
Márton