Adding worklog via API returns 403

[Robert Kölz]

Hi,

I'm trying to syncronize my worklogs via a small web application (with react) by using the jira rest api.

So far I can retriev all existing entries of an issue with a simple GET request.

But when I try to add a new entry using POST I always get an 403 error returned.

I tried with different configuration settings, but nothing got it working.

const header = new Headers(); 
const authorization = `Basic ${authorizationKey}`; 
header.append('Authorization', authorization); 
header.append('Content-Type', 'application/json');
 const proxyUrl = 'https://cors-anywhere.herokuapp.com/';
 const jsonString = JSON.stringify(requestData); 
console.log(jsonString); 
fetch(proxyUrl + targetUrl, { 
method: 'POST', 
headers: header, 
body: jsonString, }) 
.then(result => result.json()) 
.then((responseData) => { callback(responseData); }) 
.catch((error) => { console.log('post request failed', error); });

I can run the same request via Postman successfully.

So it seems not to be an authentication, data or CORS problem. 

Any hints to get this running are appreciated.

Regards,

Robert

[Leon V]

Hi Robert,

Figured this out eventually? I'm having the same exact problem you described. Not able to POST to worklog, but able to get all issues. I'm using session-cookie as authentication method.

Regards

[Leon V]

I figured it out. What fixed it for me is:

https://community.atlassian.com/t5/Jira-questions/Jira-7-rest-api-XSRF-check-failed-for-post-issue-with/qaq-p/488706

Explained here:

https://confluence.atlassian.com/jirakb/rest-api-calls-with-a-browser-user-agent-header-may-fail-csrf-checks-802591455.html?_ga=2.267212166.945929909.1587020613-1802276762.1585563718

Thanks to @Leonard Chew for pointing out