-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
None
-
Affects Version/s: 8.22.4
-
Component/s: Issue - Others
-
8.22
-
8
-
Severity 3 - Minor
-
3
Issue Summary
When having a browser tab opened to a page containing the Issue Collector form and another browser tab opened to an authenticated Jira session and having the user interacting with the authenticated Jira session, the Issue Collector returned the 'XSRF check failed' error upon submission.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Step 1: Embed an Issue Collector form into a page on some domain (domain1.com) and the Issue Collector is pulled for a Jira server with a different domain (domain2.com). Access to both the Issue Collector and Jira over HTTPS.
- Step 2: Open a browser (Chrome/Edge) with two tabs.
- Step 3: In one browser tab, load the page containing the Issue Collector form, fill it out but do not submit.
- Step 4: In a different tab (same browser), log into the Jira UI and click on a Jira issue (or any other resources in the UI).
- Step 5: Return to the browser tab containing Issue Collector form and click submit
Expected Results
The expected result is that the Issue Collector form would submit successfully
Actual Results
The actual result is that the Issue Collector form would return the error "Oops! Something went wrong..."
Below is the full error shown on the Issue Collector form:
Oops! Something went wrong... There was a problem submitting your feedback, likely due to the configuration of this form. You might want to contact the site owner to let them know about this issue.
From the Developer Tool, we observe the status code 404 is returned, as well as the error "XSRF check failed" in the Response data.
Workaround
The work-around is for the user to avoid switching back and forth between the browser tab containing the Collector form and interacting with the browser tab authenticated into the Jira session.
- mentioned in
-
Page Loading...