"Exception.Error: Access to the resource is fobidden"when trying to extract data from JIRA

[karimm]

Hi All

I have several reports based on JIRA data which are using Web Connector to connect to an internal JIRA server (v9.12.7)  and extract data into Excel and PowerBI.

Following the latest upgrade of JIRA, the power queries suddenly stopped working with the error "Exception.Error: Access to the resource is fobidden".

The URL we use is the one that the JIRA UI is using to fetch data from the server, when user selects Search->Issues->Run a filter->Export-> CSV (Current fields)

The same URL being called, if called via browser or POSTMAN, works indeed.

I know you might say the problem is in JIRA but the team is not able to find any issue.

So I would appreciate if anyone could have a look at the below excerpt from the trace logs and point to a possible direction.

P.S. the connection is using Basic authentication with username and API token.

Thank you very much in advance.

(I have masked some of the details.)

DataMashup.Trace Warning: 24579 : {"Start":"2024-04-22T09:53:12.5128087Z","Action":"Library/Common/RetryPolicy/TryExecuteAction","HostProcessId":"XXXXX","RetryAlgorithm":"ExponentialBackoff","MaxTries":"3","Attempt":"1","ResourceKind":"Web","ResourcePath":"https://XXXXXjira/XXXXX/jira.XXXXX:XXXXX-csv-current-fields/XXXXX/XXXXX.csv","Exception":"Exception:\r\nExceptionType: System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=XXXXX\r\nMessage: The remote server returned an error: (403) Forbidden.\r\nStackTrace:\n at Microsoft.Mashup.Engine1.Library.Http.WrappingHttpWebRequest.WrapExceptionResponse[T](Func`1 getValue)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.CreateResponse(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.GetResponseCore(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.RetryPolicy.Execute[TResult](IEngineHost host, IResource resource, Func`1 func)\r\n\r\n\r\n","ProductVersion":"2.126.29.0 (24.02)","ActivityId":"XXXXX-XXXXX-XXXXX-XXXXX-XXXXX","Process":"Microsoft.Mashup.Container.NetFX45","Pid":XXXXX,"Tid":1,"Duration":"00:00:00.0005019"}
DataMashup.Trace Error: XXXXX: {"Start":"2024-04-22T09:53:12.5133635Z","Action":"Library/Common/RetryPolicy/ExecuteAction","HostProcessId":"XXXXX","Exception":"Exception:\r\nExceptionType: System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=XXXXX\r\nMessage: The remote server returned an error: (403) Forbidden.\r\nStackTrace:\n at Microsoft.Mashup.Engine1.Library.Http.WrappingHttpWebRequest.WrapExceptionResponse[T](Func`1 getValue)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.CreateResponse(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.GetResponseCore(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.RetryPolicy.Execute[TResult](IEngineHost host, IResource resource, Func`1 func)\r\n\r\n\r\n","ProductVersion":"2.126.29.0 (24.02)","ActivityId":"XXXXX-XXXXX-XXXXX-XXXXX-XXXXX","Process":"Microsoft.Mashup.Container.NetFX45","Pid":XXXXX,"Tid":1,"Duration":"00:00:00.0000621"}

DataMashup.Trace Error: XXXXX: {"Start":"2024-04-22T09:53:11.5880899Z","Action":"Engine/IO/Web/Request/GetResponse","ResourceKind":"Web","ResourcePath":"https://XXXXXjira/XXXXX/jira.XXXXX:XXXXX-csv-current-fields/XXXXX/XXXXX.csv","HostProcessId":"XXXXX","RequestMethod":"GET","RequestUri":"https://deljira/XXXXX/jira.XXXXX:XXXXX-csv-current-fields/XXXXX/XXXXX.csv?jqlQuery=key=XXXXX-XXXXX","RequestHasContent":"False","RequestHasHeaders":"False","RequestHasTimeout":"True","UseCache":"True","UseBuffer":"True","StatusCode":"Forbidden","StatusDescription":"","Exception":"Exception:\r\nExceptionType: System.Net.WebException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=XXXXX\r\nMessage: The remote server returned an error: (403) Forbidden.\r\nStackTrace:\n at Microsoft.Mashup.Engine1.Library.Http.WrappingHttpWebRequest.WrapExceptionResponse[T](Func`1 getValue)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.CreateResponse(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.GetResponseCore(ResourceCredentialCollection credentials)\r\n at Microsoft.Mashup.Engine1.Library.Http.RetryPolicy.Execute[TResult](IEngineHost host, IResource resource, Func`1 func)\r\n at Microsoft.Mashup.Engine1.Library.Http.Request.GetResponse(ResourceCredentialCollection credentials, RetryPolicy retryPolicy, SecurityExceptionCreator securityExceptionCreator, Boolean tokenRefreshed)\r\n\r\n\r\n","ProductVersion":"2.126.29.0 (24.02)","ActivityId":"XXXXX-XXXXX-XXXXX-XXXXX-XXXXX","Process":"Microsoft.Mashup.Container.NetFX45","Pid":XXXXX,"Tid":1,"Duration":"00:00:00.9257152"}

[johnbasha33]

@karimm 

The error message "403 Forbidden" typically indicates that the server understood the request but refuses to authorize it. This suggests that the issue might be related to the authentication mechanism used by the JIRA server or the permissions assigned to the user or API token being used for authentication.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. **Check Authentication Credentials**: Ensure that the username and API token being used for Basic authentication are correct and have the necessary permissions to access the requested resource in JIRA. Double-check that the credentials have not expired or been revoked.

2. **Review JIRA Server Configuration**: Verify that the JIRA server configuration allows access to the resource being requested via the Web Connector. Check if there are any restrictions or security settings that could be causing the server to reject the request with a "403 Forbidden" error.

3. **Test Authentication Outside Power BI**: Use tools like Postman or cURL to manually send requests to the JIRA server using the same URL and authentication credentials. This can help verify if the authentication process is working correctly outside of Power BI.

4. **Inspect Request Headers**: Check the headers being sent with the request to see if there are any issues with the authentication headers or other request parameters. Ensure that the headers are formatted correctly and include all necessary information for authentication.

5. **Review Server Logs**: Check the server logs on the JIRA server to see if there are any additional details or error messages that could provide insight into why the request is being rejected with a "403 Forbidden" error.

6. **Contact JIRA Support**: If you are unable to resolve the issue through troubleshooting, consider reaching out to Atlassian support or your organization's JIRA administrators for assistance. They may be able to provide further guidance or troubleshoot server-side issues that could be causing the error.

By following these steps and investigating the potential causes of the "403 Forbidden" error, you should be able to identify and resolve the issue with accessing JIRA data via the Web Connector in Power BI.

Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!

[karimm]

Thank you for you quick response.

I have sent this to the support teams.