XSRF token validation failure in EKS

robotsnoindex

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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_REFERRER error when trying to save an edited resource or configuration.

Environment

  • Helm chart deployment of Bamboo DC

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.



Last modified on Mar 7, 2025

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.