'XSRF white list failure' When Editing Workflows

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

When you try to perform some edit actions with existing workflows, as changing post-functions and add validators, you may get a XSRF white list failure error exception.

The following appears in the atlassian-jira.log:

1 2 3 4 5 6 7 8 Cause: java.lang.RuntimeException: XSRF white list failure Stack Trace: [hide] java.lang.RuntimeException: XSRF white list failure at com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor$CallStack.isProtectedAction(XsrfVulnerabilityDetectionSQLInterceptor.java:180) at com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor.afterExecutionImpl(XsrfVulnerabilityDetectionSQLInterceptor.java:75) at com.atlassian.jira.security.xsrf.XsrfVulnerabilityDetectionSQLInterceptor.afterSuccessfulExecution(XsrfVulnerabilityDetectionSQLInterceptor.java:40) ...

Cause

This occurs only if using the EAR/WAR distribution. When Jira checks the classes directory, it finds unexpected unknown jar files and so throws the XSRF white list failure regarding the system security.

Resolution

  1. Shutdown your instance.

  2. Navigate to <tomcat>/lib directory.

  3. Look for any files which doesn't match with the application originals and move off the directory.

  4. Start JIRA.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.