RE: Jira 4.1 SOAP errorsRE: Jira 4.1 SOAP errorshttps://www.klaros-testmanagement.com/en/c/message_boards/find_thread?p_l_id=11703&threadId=586652024-03-28T17:09:44Z2024-03-28T17:09:44ZJira 4.1 SOAP errorsMarkus Krieghttps://www.klaros-testmanagement.com/en/c/message_boards/find_message?p_l_id=11703&messageId=586642013-12-11T12:25:04Z2013-12-11T12:25:04Zwe are testing here with both Jira 4.0.1 and Jira 4.1.2 systems.<br /><br />* 4.0.1: creating issues works fine after settings all fields to optional that are not part of the Klaros form<br /><br />* 4.1.2: we get errors even with the default Jira create issue form<br /><br />after checking the Tomcat console it looks like Jira 4.1.x has a tighter security and that specifically a form token is not valid any longer; see here for details: http://confluence.atlassian.com/display/JIRA/Disabling+Form+Token+Checking?clicked=jirahelp<br /><br />so either you have to update you help to tell Jira users to change the setting <br />jira.xsrf.enabled=false<br />in jira-application.properties or you might need to change the SOAP code for creating new issues.Markus Krieg2013-12-11T12:25:04ZRE: Jira 4.1 SOAP errorsTorsten Stolpmannhttps://www.klaros-testmanagement.com/en/c/message_boards/find_message?p_l_id=11703&messageId=586892013-12-11T12:25:04Z2013-12-11T12:25:04Z<div class="quote"><div class="quote-content">4.0.1: creating issues works fine after settings all fields to optional that are not part of the Klaros form</div></div><br /><br />From JIRA's point of view it is sensible to behave in such a way. We need to get a proper support for custom fields in IM's to get this working, as discussed via mail.<br /><br /><div class="quote"><div class="quote-content">4.1.2: we get errors even with the default Jira create issue form<br /><br />after checking the Tomcat console it looks like Jira 4.1.x has a tighter security and that specifically a form token is not valid any longer; see here for details: http://confluence.atlassian.com/display/JIRA/Disabling+Form+Token+Checking?clicked=jirahelp<br /><br />so either you have to update you help to tell Jira users to change the setting<br />jira.xsrf.enabled=false<br />in jira-application.properties or you might need to change the SOAP code for creating new issues.</div></div><br /><br />Thanks a lot for providing a solution here!<br /><br />I raised an issue to provide better support for JIRA 4.1 here (KLAROS-950 - The support for JIRA breaks with JIRA 4.1.2 without disabled form token).<br /><br />Regards,<br /><br />TorstenTorsten Stolpmann2013-12-11T12:25:04Z