-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
1
-
Severity 3 - Minor
-
1
-
Summary
There are Jira issue macros with URLs such as
<ac:structured-macro ac:name="jiraissues" ac:schema-version="1" ac:macro-id="ca8f02ed-018d-43c6-a8da-xxxxxxxxxxxx">
<ac:parameter ac:name="cache">off</ac:parameter>
<ac:parameter ac:name="count">true</ac:parameter>
<ac:parameter ac:name="title">Umgesetzte Änderungen</ac:parameter>
<ac:parameter ac:name="url"><ri:url ri:value="https://{cloud-url}.atlassian.net/sr/jira.issueviews:searchrequest-xml/21119/SearchRequest-21119.xml?tempMax=1000" /></ac:parameter>
<ac:parameter ac:name="height">250</ac:parameter>
</ac:structured-macro>
Even after updating the base URL as you can see in the above metadata, the macros is still not fixed.
Observation
When visiting the partially fixed link from the storage format
https://{cloud-site}.atlassian.net/sr/jira.issueviews:searchrequest-xml/21119/SearchRequest-21119.xml?tempMax=1000
We get an "XSRF Security Token Missing", this may be due to an OAuth error. In Jira and Confluence Cloud, we regularly run health checks to ensure that the OAuth connection is secure. Any time Jira searches are run from outside Jira (Confluence is outside Jira), then a valid, non-expired token is required. To replicate, if we go to:
> https://{cloud-site}.atlassian.net/issues/?filter=21119
> Then click "Export" (top right corner)
> Then click "Export XML", and then we'll see a valid search.
> If we inspect the URL bar, you will see:
> https://{cloud-site}.atlassian.net/sr/jira.issueviews:searchrequest-xml/21119/SearchRequest-21119.xml?atl_token=549xxxxxxxxxxxxxxxxxxxxxxxxxxxx48_lin&tempMax=1000
The addition of an "atl_token" parameter. This is missing from the Jira issue macro in Confluence - it is not able to perform an authenticated valid search as it is missing a token.
Next Steps:
There is no known workaround.
- mentioned in
-
Page Loading...