How to finalize publishing Oauth 2.0 app in Marketplace?

[Dason]

Hi All,

I'd like to know how I can publish my Oauth 2.0(3LO) Application so that I can distribute our integration to customers when it goes into production.

I have already come across the form to fill the required data to make an public. However was not able to quite conclude how the inputs should be given.

Please let us know how the form would be filled when the app is an OAuth app. For example what should the learn more Url include? would a  drive link suffice? and is the app key an identifier constructed from our end? 

Thanks in Advance!

[Hugo Mora]

Two different things, and only the first is required to ship.

1. Make the app usable (developer console). A 3LO app is private by default — only you can use it. Go to your app → Distribution → enable sharing, filling the mandatory fields: Vendor (your company), Privacy policy URL, and the personal-data declaration (if Yes, you must also add the Personal data reporting API under Permissions and tick the confirmation). Then Authorization → OAuth 2.0 (3LO) → Configure → copy the authorization URL and embed it in your product's "Connect to Jira" button. That's it — customers can now authorize in production.

2. Marketplace listing (optional). This is only needed to remove the "not reviewed by Atlassian" warning on the consent screen and to be discoverable. On Publish a new app, choose "My app isn't directly installable".

• App key — you invent it. Reverse-DNS, e.g. com.yourcompany.product.jira. Immutable once set, and unrelated to your OAuth client ID.
• Learn more URL — under App file location, pick "provide another URL". A Drive link won't do: it must be publicly reachable with no login, on your own domain — a product/docs page saying what the integration does, which scopes it needs, and how to connect.
• Rest: version 1.0.0, build number (usually auto), name per branding guidelines ("X for Jira", not "Jira X"), compatible application = Jira Cloud.

For the review, send a test account for your software plus a setup walkthrough up front — that's the main thing that speeds it up.

One design check: build a single shared 3LO app. Asking customers to create their own 3LO apps or hand over API tokens now breaches Atlassian's cloud security requirements.

--Hugo