Jira 4.1 SOAP errors - Klaros Test Management - Forum - Klaros Test Management
Jira 4.1 SOAP errors
Markus Krieg, modified 10 Years ago.
Jira 4.1 SOAP errors
Padawan Posts: 34 Join Date: 8/23/10 Recent Posts
we are testing here with both Jira 4.0.1 and Jira 4.1.2 systems.
* 4.0.1: creating issues works fine after settings all fields to optional that are not part of the Klaros form
* 4.1.2: we get errors even with the default Jira create issue form
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
so either you have to update you help to tell Jira users to change the setting
jira.xsrf.enabled=false
in jira-application.properties or you might need to change the SOAP code for creating new issues.
* 4.0.1: creating issues works fine after settings all fields to optional that are not part of the Klaros form
* 4.1.2: we get errors even with the default Jira create issue form
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
so either you have to update you help to tell Jira users to change the setting
jira.xsrf.enabled=false
in jira-application.properties or you might need to change the SOAP code for creating new issues.
Torsten Stolpmann, modified 10 Years ago.
RE: Jira 4.1 SOAP errors
Jedi Council Member Posts: 755 Join Date: 2/12/09 Recent Posts4.0.1: creating issues works fine after settings all fields to optional that are not part of the Klaros form
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.
4.1.2: we get errors even with the default Jira create issue form
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
so either you have to update you help to tell Jira users to change the setting
jira.xsrf.enabled=false
in jira-application.properties or you might need to change the SOAP code for creating new issues.
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
so either you have to update you help to tell Jira users to change the setting
jira.xsrf.enabled=false
in jira-application.properties or you might need to change the SOAP code for creating new issues.
Thanks a lot for providing a solution here!
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).
Regards,
Torsten