Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Rest Api using Oauth 2 authentication returns 403

Malcolm
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 14, 2018

Hi,

We (Zoho Assist) are planned to integrate our product with Jira Cloud Platform. We chose OAuth 2 authentication model for using Jira Rest Api's. We are facing some issues in getting Jira Issue Details. 

Getting Refresh Token and stored in our instance is successfully completed.  

OAuth 2 Scopes:

write:jira-work read:jira-work read:jira-user offline_access

 

We are able to get access_token from stored refresh token using Token Url.

 

We can get available resource (cloud_id, name , scopes , avatarUrl) using access token  by below api

https://api.atlassian.com/oauth/token/accessible-resources

Jira-Success-1.png

 

But we are facing issues while getting Jira Issue Details with same access token by below api.

https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/issue/{issueKey}

 

Jira-Forbidden-2.png

 

Always it returns 403.

 

It works while we tried to  get Jira Issue Details using Basic Authentication. So we are expecting that there may be issue in OAuth2 model or we may miss something. Help us to sort out this problem.

 

Note: It was working for long time. We are facing issues from last Thursday (Oct 12).

Check and let we know if we miss anything related to Oauth2.

 

 

1 answer

0 votes
Deleted user October 15, 2018

You may need to generate a new Oauth2 token through the authentication endpoint

Malcolm
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 15, 2018

Hi, 

I have tried that too. But it doesn’t works. I think problem may be in between api.atlassian.com and Jira Instance (rest api).

Kindly try to get jira issue details for Jira instance using OAuth 2 and let me know how u achieved it.

 

It was working perfectly since last Thursday (Oct 12). So I guess this may be issue.

Suggest an answer

Log in or Sign up to answer