Data connection throws 498 HTTP response with error "Invalid JSON document"

Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.

Summary

When you try to create a data connection, you get an error HTTP Response: 498

Invalid JSON document

Connected to the page but the data returned does not appear to be a valid JSON document.

Environment

Jira Cloud

Diagnosis

The JSON object that you are using contains an invisible byte order mark character at the beginning. According to the JSON standard, JSON text should not begin with a byte order mark, and this is the reason that our JSON parser rejects the supplied value. 

 If you open the URL in the Mozilla(or other) browser you can see errors like:

SyntaxError: JSON.parse: unexpected character at line 1 column 482013 of the JSON data

Trying to validate the JSON, you can see the below errors:

Parse error on line 1:
...", "echeStartDate": NaN, "echeEndDate": 
-----------------------^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'

Cause

The additional space or invalid character at the beginning of the JSON text. 

We did have known bugs with certificate issues by Sectigo but this has been fixed now.

JRACLOUD-76343 - Cloud products are not trusting Certificates issued by Sectigo


Solution

  • Review the JSON data to remove the invalid character. A simple workaround would be to prepare a JSON object that does not begin with this character.
  • Verify that the certificates are valid 
  • If you still encounter an issue please contact Atlassian Support






Last modified on Jan 23, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.