Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

XSRF Security Token error on Issue Creation on Project with Behaviours enabled

Javier Castro June 11, 2019

I have an instance of JIRA 7.7.1 with the Adaptavist Script Runner 5.3.7 plugin installed.

I have created some Behaviours for a specific project and issue type. This project has an associated workflow in which the validator "ScriptRunner workflow function - Custom script validator (inline script)" is used in the "Create" transition to check that some fields have the appropriate value.

When I fill everything correctly to the first one, I can create the issue without problems. But if I fill in some field incorrectly (and therefore the validator returns an InvalidInputException), after correcting it and clicking again on the "Create" button, I get an "XSRF Security Token Missing" error:

 

xsrfTokenError.png

If I delete my project and issue type from the Behaviours Mapping list, this does not occurs, and I can create the issue regardless of whether it fills in all the fields correctly the first time, or that I have to correct any of them.

Why does this problem occur? How can I solve it?

 

1 answer

0 votes
Joel
Contributor
April 2, 2020

Almost a year later and no answer!? You've got to be kidding me!? I have this same issue and I'd imagine I'm not the only one. I'm working with a behavior for my customer that incorporates validation on the description field and I'm running into the same issue. 

Javier Castro April 2, 2020

I contacted ScriptRunner support and they asked me for the following information so they could replicate the problem:

  • JIRA version
  • ScriptRunner version
  • Groovy Behavior scripts
  • Groovy scripts for workflow validators

After a few days they answered me saying that they couldn't replicate the problem, and that I try to update ScriptRunner to see if that fixes the problem.
After updating ScriptRunner, I have not had this problem again. Maybe updating ScriptRunner will also solve the problem for you

Like Joel likes this
Joel
Contributor
April 2, 2020

Thank you Javier! I'll give it a shot. We were on 5.6.13. Going to 5.8.

Joel
Contributor
April 2, 2020

Sadly this did not fix the problem @Javier Castro .

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events