JIRA connect app vs OAuth2.0

vineet_kumar_7k7i2u

I have a project where I have to create JIRA issues programmatically but I am bit confused which way I should go.

Our application does some work and responsible to create JIRA tickets based on certain criteria  so we will have to store the keys of customers in case of OAuth2.0 and for JIRA connect this does not sound related to market place as we are not offering anything here.

 

Please let me know what is the best way to achieve this ??

Andy Heinzer

Either method can be used to make REST API calls to Jira Cloud, and both can be used to create issues on behalf of specific users (impersonation). The key difference here is how you are planning to build the app itself.  If you are planning to use the Connect framework, then you will end up using a JWT token as explained in Security for Connect apps.

However if you're not building a Connect app, or using the Forge framework, then you could be creating your app in some other framework and in turn you would then be expected to be using OAuth 2.0.  If that is the case, then check out OAuth 2.0 (3LO) apps as it explains in more detail how your application is expected to manage the OAuth handshake.