Strategy for integrating existing app with JIRA/Confluence REST APIs: application links or apps?

[Brian Levine]

We have an existing in-house app that we plan to integrate with our JIRA/Confluence installation.  Primarily, we'll be executing search requests from this app against JIRA/Confluence.

The documentation here, details how to accomplish this using Application Links and Oauth1.0a. However, it also states that using Oauth2 for apps is preferred which is documented here. This mechanism appears to still be in developer preview.

So my questions:

1. Should I move forward with using Application Links and OAuth 1.0a now?
2. If I do decide to move to OAuth2 for apps, do I have to publish my app to the marketplace?  This app would only be used internally and we don't really want to make it public.  In other words, is there support for "locally published" apps?

[Anton Chemlev - Toolstrek -]

Hi,

Since you have your own home-brewed app, it is better to use plain old OAuth 1.0a with Application Links. Here's a great article - https://medium.com/mibexsoftware/how-to-use-oauth-with-atlassian-products-c0f357ae91eb.

We also have our own app, which sits between Jira and Slack. It talks to Jira via OAuth/Application Links.

[Brian Levine]

Thanks Anton. I'd prefer to use OAuth2, but if this isn't supported (except by implementing an 'app', then OAuth1.0a will have to do.  But aside from that, do you know whether there will be such a thing as "locally published" apps in the future?

[Anton Chemlev - Toolstrek -]

It seems to me no, but who knows. For now Plugins2 framework plugins are the only solution for server edition.