How to support Oauth 2.0 for webhooks in Jira ??

[shubham tak]

I am developing an app and I need to have Jira webhook support for my app. Also, I need Jira OAuth 2.0 authentication for my app as it provides better security. I tried to use OAuth 2.0 for all the API's mentioned in the Jira API documentation, almost every API is working except the webhook. Can you tell me why I am not being able to run webhook APIs with OAuth 2.0 authentication and if there is a way then how it is possible?? 

I saw Zapier uses Oauth 2.0 in their applications so I wanted to know that how can I also use it in webhooks?? 

[Petter Gonçalves]

Hello @shubham tak

Thank you for reaching out.

Can you please confirm what is the exact call (hiding your domain) you are trying to run and confirm if you are running your app using Atlassian Connect?

as mentioned in the documentation below, you cannot use OAuth 2.0 (3LO) with Atlassian Connect apps. OAuth 2.0 (3LO) is used to allow external applications (Including Zapier) and services to access Atlassian product APIs on a user's behalf:

OAuth 2.0 (3LO) for apps 

Additionally, since this is a development question, I believe the best place to ask for help is in the Atlassian Developer Community:

https://community.developer.atlassian.com/ 

The mentioned portal was specifically created for development questions, where you will find articles and suggestions from other third-party partners and Atlassian developers. Feel free to open a new topic about your question there or search for similar topics about yous.

Let us know if you have any other questions.

[shubham tak]

Thank you so much for your help. I am currently using an external app instead of an Atlassian connect app that is why I am confused because in the documentation it is mentioned that for external apps OAuth 2.0 is allowed for webhooks but still when running an API it is showing that OAuth 2.0 is not yet supported for webhooks and its still under development

[gabriel]

For what it's worth, my team is experiencing the same roadblock. We've set up one of the new-style OAuth 2.0 (3LO) apps but are unable to hit any webhook-related REST API endpoints. This shortcoming is mentioned in the docs (only Connect apps can interact with webhook endpoints apparently) and there's an open ticket about it, though it doesn't seem to be on anyone's radar.

@Petter Gonçalvesany way we could have this addressed or prioritised? Thanks so much!