KB483584: Web 11.0 and 2019 Stops Responding When Using Report Filters

Description

SAML authentication is available only for Strategy Web. When an environment is protected by SAML, there might be issues when working with report filters.
When following the steps to reproduce, the UI might stop responding. It is due to Spring security filters that are underlying foundation for SAML integration.
The same manipulations on reports done in Developer will not reproduce the issue.

Steps to Reproduce

1. Log in to Strategy Web using SAML.
2. Create new report -> blank report.
3. Add an attribute to the grid.
4. Drag the attribute to the report filter area.
5. Try clicking the select button under qualify in the report filter.
6. Notice the button is non-responsive.

Alternative steps

1. Log in to Strategy Web using SAML.
2. Run a report.
3. Select "Add condition" in the view filter area.
4. Select an attribute.
5. Watch the loading icon spin with no result.

Why is this happening?

The interface does not react as expected due to security filters introduced with Spring Security filters. When SAML is enabled, the response headers will contain

X-Frame-Options DENY

, which prevents frames from being displayed.

Solution

The issue has been fixed in Update 1 for Strategy 2019 (11.1) and further updates.

Workaround

1. Navigate to the

   SpringSAMLConfig.xml

   file.
   One common location is as follows (Linux example), it may be different in your case:
   

   /opt/apache/tomcat/apache-tomcat-9.0.12/webapps/MicroStrategy/WEB-INF/classes/resources/SAML

2. Once you locate this file, under the

   <security:http>

   XML tag, include the following:
   

   
   <security:headers>
   <security:frame-options disabled="true">
   </security:frame-options>
   </security:headers>
   

   
   
3. Restart Tomcat and check to see if the issue is resolved.