My app suddenly does not work anymore

[Eric Gavaldo]

Hi Guys,

I didn't change my app (XStudio) for month but suddenly, when I press the configure button, nothing happens, the configuration screen does not appear, I don't see anything abnormal in the log but I only get a popup "Something's gone wrong - Our team has been notified. If the problem persists, please contact Atlassian Support".

Did someone already experienced this ?

Is it really something wrong Atlassian side ? How can I know ?

Thanks,

[Mikael Sandberg · Accepted solution]

You may want to contact the vendor for the app and see if anything is going on on their end.

Have you tried using an incognito window and see if the issue persist? Also try clearing your browser cache from all time and see if that helps.

[Eric Gavaldo]

We are the App vendor.

We saw the problem was due to X-Frame-Options set to Deny in the App server's response.

If someone has the issue, here is the solution:

This problem appears as soon as you configure the tomcat hosting the App so that it matches Atlassian requirement for HSTS.

Basically for HSTS we had to add this filter:

<filter>
<filter-name>httpHeaderSecurity</filter-name>
<filter-class>org.apache.catalina.filters.HttpHeaderSecurityFilter</filter-class>
<async-supported>true</async-supported>
<init-param>
<param-name>hstsEnabled</param-name>
<param-value>true</param-value>
</init-param>
<init-param>
<param-name>hstsMaxAgeSeconds</param-name>
<param-value>31536000</param-value>
</init-param>
<init-param>
<param-name>hstsIncludeSubDomains</param-name>
<param-value>true</param-value>
</init-param>
</filter>

From then, we had the issue with X-Frame-Options set to deny.

I guess this is the default init param in any filter.

so to fix the X-Frame-Option issue, we had to add this:

<init-param>
<param-name>antiClickJackingEnabled</param-name>
<param-value>false</param-value>
</init-param>

In the filter

Thanks,