XSRF token validation failure in EKS

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

Summary

When Bamboo is setup on a Kubernetes cluster, you may get an XSRF_FAILUER_NO_REFERRERerror when trying to save an edited resource or configuration.

Environment

  • Helm chart deployment of Bamboo

Diagnosis

  • Check the Ingress controller CORS policy and confirm what Referrer policy applied.

Cause

  • The Referrer Policy is no-referrer or any other policy which do not include any referrer information.

Solution

  • Use a referrer policy which includes the referrer information to requests. e.g STRICT-ORIGIN-WHEN-CROSS_ORIGIN.

Updated on March 6, 2025

Still need help?

The Atlassian Community is here for you.