Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
711:import_reports [2025/07/25 14:47] – [Reporting (Advanced)] Weinlein, Thomas711:import_reports [2025/07/25 15:06] (current) – [Reporting (Advanced)] Weinlein, Thomas
Line 18: Line 18:
  
 ===== Reporting (Advanced) ===== ===== Reporting (Advanced) =====
 +
 +=== Security restrictions ===
  
 Access to persistent global variables is not allowed for reports in Stages, due to security implications. E.g. Access to persistent global variables is not allowed for reports in Stages, due to security implications. E.g.
Line 35: Line 37:
 </code> </code>
  
-The access of custom event handler scripts to BIRT and other Java classes is highly restricted to keep the Stages server secure. In case additional classes need to be whitelisted (there are errors logged in case the system does not allow the access) and the security implications are acceptable, add the following parameter to the reporting context in the ''server.xml'' and adapt the value accordingly.+The access of custom event handler scripts to BIRT and other Java classes is highly restricted to keep the Stages server secure. In case additional classes need to be whitelisted there are errors logged that the system does not allow the access to those classes. 
 + 
 +In case the security implications are acceptable, add the following parameter to the reporting context in the ''server.xml'' and adapt the value accordingly.
 <code xml> <code xml>
 <Context path="/reporting" [...]> <Context path="/reporting" [...]>
Line 43: Line 47:
 </code> </code>
  
 +
 +To whitelist additional classes for **Stages data source** scripts add the following config property to config.xml.
 +<code xml>
 +<property name="metrics.script.class.whitelist" value="java.time.Instant,java.time.Duration"/>
 +</code>
  
 ==== Direct database access in reports ==== ==== Direct database access in reports ====