Jira 4.1 SOAP errors

Markus Krieg, geändert vor 10 Jahren.

Jira 4.1 SOAP errors

Padawan Beiträge: 34 Beitrittsdatum: 23.08.10 Neueste Beiträge
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.
thumbnail
Torsten Stolpmann, geändert vor 10 Jahren.

RE: Jira 4.1 SOAP errors

Jedi Council Member Beiträge: 755 Beitrittsdatum: 12.02.09 Neueste Beiträge
4.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.


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