Unable to create new issues after upgrading to Jira 7
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
The content on this page relates to platforms which are not supported. Consequently, Atlassian Support cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.
Users are unable to create any issue, when the "Create" issue button is clicked the browser returns below error:
- Issue happens after upgrading to JIRA 7
- JIRA instance behind a reverse proxy
- atlassian-jira.log is throwing below XSRF check errors
2016-03-24 11:41:39,639 http-nio-8080-exec-9 WARN username 701x48328x3 1sx07jj 10.50.8.252,127.0.0.1 /rest/webResources/1.0/resources [c.a.p.r.c.security.jersey.XsrfResourceFilter] Additional XSRF checks failed for request: http://jiradev.domain.com/rest/webResources/1.0/resources , origin: null , referrer: https://jiradev.domain.com/secure/Dashboard.jspa , credentials in request: true , allowed via CORS: false
Tomcat is not "aware" of the reverse proxy due to "proxyName" and "proxyPort" are not specified in the connector in server.xml. As a result the browser request is blocked, due to REST API not receiving the expected hostname/port from the origin header value.
Specify the proxyName and proxyPort parameters in server.xml, for example:
<Connector port="8080" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true" proxyName="jiradev.domain.com" proxyPort="443" scheme="https"/>
In this example, jiradev.domain.com would be the URL that users use to access JIRA through the proxy.