CSRF Token in Request Does Not Match Value in Session Cache

Published Date: July 17, 2025

Products and Versions Covered: 

• Jama Connect® All version
  • Cloud/CVC
  • Self-hosted, Replicated - KOTS

Summary

Received a “CSRF token in request did not match value in the session cache” error in the browser. This suggests that stale CSRF tokens, possibly cached alongside old session information, are being reused, leading to token mismatches. 

Resolution

1. Clear your browser cache and cookies
2. Reload the page before retrying the action.

Additional Resources 

• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.