we have followed the documentation for the implementation. but we are receiving 401 unauthorized even though right scopes and tokens are provided. please confirm whether webhook registration with OAuth2.0 is working or not? Please confirm this ASAP.
our request looks like this
Hi @Jaswanth Boyidi name , welcome to the Community!
It looks like the Authorization header is what's causing the problem. In the example above, a Bearer type token is used. Atlassian Cloud's authorization uses tokens generated from id.atlassian.com , but these tokens go in place of what would typically be the password in user/pass type authorization. So your example:
curl --location --request POST 'https://XXXXX.atlassian.net/rest/api/2/webhook' \
--header 'Authorization: Bearer XXXXXXXXX' \
curl --location --request POST 'https://XXXXX.atlassian.net/rest/api/2/webhook' \
--user 'email@example.com:<api_token>' \
Hi @Daniel Eads ,
so Isn't it possible to register webhooks with OAuth2.0(3LO) using Bearer <Accesstoken>, as using the email address and api_token will be Basic Auth. could you please confirm if it is possible with OAuth2.0(3LO) using Bearer <Accesstoken>. sorry in advance if I'm wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you managed to find out how to solve your issue? I am having similar difficulties
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @ante
yes, got a solution for this, please refere to this discussion https://community.developer.atlassian.com/t/oauth-2-0-3lo-app-encounters-401-unauthorized-trying-to-create-webhooks/54862
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jaswanth Boyidi name , exactly what I was looking for. Thank you very much
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.