You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our Security sca
ns showed that the Atlassian DC Applications we have hosted (Jira, Confluence.. ) are lacking Security related Headers especially "Clear-Site-Data".
We have tried setting the headers on haproxy side, however it resulted in user's sessions getting timed out with each page navigation request.
This is what we have tried:
http-response set-header Clear-Site-Data: "cache", "cookies", "storage", "executionContexts", "*"
1) Is the Clear-Site-Data header required at a Global level for all page 'responses', OR should it be set only when the user tries to log out of Jira/ closes the tab ??
- If it's the former, will it clear the stored session of logged in user ?
- If it's the latter, how can we target the logout request alone ?
2) Do you have any docs/ tickets which talks about the syntax required for 'Clear-Site-Data' header to be set for Atlassian applications ?? ( I found this ticket : [https://jira.atlassian.com/browse/JRASERVER-71365\](https://jira.atlassian.com/browse/JRASERVER-71365))
The Clear-site-data should only be used on logging out (or timing out, but that doesn't get done by the server and browser). The cache that it causes it to clear includes the current logged in session and entered data, so having that header on most responses would destroy the ability to actually use the system.
There is only one URL that I know of that goes through a log-out, so you could either hack the code that generates the page to add the header, or tell your proxy to inject it only on that page.
I haven't found anything beyond the two links you have, I'm sorry.