Embed to Website: Difference between revisions

From QPR ProcessAnalyzer Wiki
Jump to navigation Jump to search
Line 2: Line 2:


== Change CSP frame-ancestors setting ==
== Change CSP frame-ancestors setting ==
By default, the Content-Security-Policy HTTL header '''frame-ancestors'' directive is set to '''<nowiki>'self'</nowiki>'''
By default, the Content-Security-Policy HTTL header '''frame-ancestors'' directive is set to '''self''', allowing the parent website where QPR ProcessAnalyzer is embedded to, to be located in the same origin. If the parent website is in another origin, the CSP needs to be changed as follows (allowing to embed QPR ProcessAnalyzer in the example.com website):
<pre>
frame-ancestors 'self' example.com;
</pre>
 
More information about the Content-Security-Policy HTTL header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP.

Revision as of 22:29, 17 September 2025

QPR ProcessAnalyzer can be embedded to another website, such as Microsoft Sharepoint. The embedding is based on the iframe html element. By default, QPR ProcessAnalyzer only allowes to be embedded by a website in the same origin that is restricted by the Content-Security-Policy HTTL header. More information how to change the CSP setting in Security Hardening.

Change CSP frame-ancestors setting

By default, the Content-Security-Policy HTTL header frame-ancestors directive is set to self', allowing the parent website where QPR ProcessAnalyzer is embedded to, to be located in the same origin. If the parent website is in another origin, the CSP needs to be changed as follows (allowing to embed QPR ProcessAnalyzer in the example.com website):

frame-ancestors 'self' example.com;

More information about the Content-Security-Policy HTTL header: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP.