Embed to Website - Revision history

MarHink: Added required change details on Cross-Origin-Opener-Policy header.

2025-11-11T12:58:02Z

Added required change details on Cross-Origin-Opener-Policy header.

← Older revision		Revision as of 12:58, 11 November 2025
Line 27:		Line 27:

	If the browser has popup blocking enabled, the new window cannot open. In such cases, a descriptive message prompts the user to disable popup blocking. Additionally, the user can manually open the authentication window by clicking the embedded frame, even if popups are blocked. Once the identity provider login is successful, the new window will close, and the original browser window will redirect to QPR ProcessAnalyzer. However, if the separate browser window is closed before completing the login, the original window will display the standard QPR ProcessAnalyzer login view.		If the browser has popup blocking enabled, the new window cannot open. In such cases, a descriptive message prompts the user to disable popup blocking. Additionally, the user can manually open the authentication window by clicking the embedded frame, even if popups are blocked. Once the identity provider login is successful, the new window will close, and the original browser window will redirect to QPR ProcessAnalyzer. However, if the separate browser window is closed before completing the login, the original window will display the standard QPR ProcessAnalyzer login view.

			In addition, for SAML authentication to work correctly when the identity provider is located on a '''different origin''' than the QPR ProcessAnalyzer server itself, the <code>Cross-Origin-Opener-Policy</code> HTTP header must be changed from its default value of <code>"same-origin"</code> to <code>"unsafe-none"</code>.
			----'''Additional Information:'''

			* '''Cross-Origin-Opener-Policy (COOP) Header:''' This is a response header that provides a way for a document to control whether a new document opened in a top-level context (like a new tab or window) shares the same browsing context group as its opener. Setting it to <code>unsafe-none</code> allows the cross-origin authentication flow to complete successfully in this embedded scenario. For more technical details, see https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Cross-Origin-Opener-Policy

Ollvihe: /* Change CSP frame-ancestors setting */

2025-11-11T11:02:15Z

Change CSP frame-ancestors setting

← Older revision		Revision as of 11:02, 11 November 2025
Line 14:		Line 14:

	== Change CSP frame-ancestors setting ==		== 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):		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>		<pre>
	frame-ancestors 'self' example.com;		frame-ancestors 'self' example.com;

Ollvihe: /* Example webpage */

2025-10-26T20:15:43Z

Example webpage

← Older revision		Revision as of 20:15, 26 October 2025
Line 1:		Line 1:
	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 allows 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 [[QPR_ProcessAnalyzer_Security_Hardening#HTTP_Response_Headers\|Security Hardening]]. Note also the special behavior when using the [[#Using_SAML_authentication_with_embedding\|SAML authentication with embedding]].		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 allows 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 [[QPR_ProcessAnalyzer_Security_Hardening#HTTP_Response_Headers\|Security Hardening]]. Note also the special behavior when using the [[#Using_SAML_authentication_with_embedding\|SAML authentication with embedding]].

	== Example webpage ==		== Example embedding webpage ==
	This is a simple example page containing an iframe element that embeds QPR ProcessAnalyzer.		This is a simple example page containing an iframe element that embeds QPR ProcessAnalyzer.

Ollvihe at 20:15, 26 October 2025

2025-10-26T20:15:22Z

← Older revision		Revision as of 20:15, 26 October 2025
Line 1:		Line 1:
	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 [[QPR_ProcessAnalyzer_Security_Hardening#HTTP_Response_Headers\|Security Hardening]].		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 allows 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 [[QPR_ProcessAnalyzer_Security_Hardening#HTTP_Response_Headers\|Security Hardening]]. Note also the special behavior when using the [[#Using_SAML_authentication_with_embedding\|SAML authentication with embedding]].

	== Example webpage ==		== Example webpage ==

Ollvihe: /* Using SAML authentication with embedding */

2025-10-26T20:13:57Z

Using SAML authentication with embedding

← Older revision		Revision as of 20:13, 26 October 2025
Line 24:		Line 24:

	== Using SAML authentication with embedding ==		== Using SAML authentication with embedding ==
	When QPR ProcessAnalyzer is embedded to another website ~~and~~ the [[SAML_2.0_Federated_Authentication\|SAML authentication]] ~~is in use~~, the authentication is ~~performed~~ in a separate browser window or tab. This is because some identity providers ~~don't allow the~~ authentication ~~to be performed in as~~ embedded (~~in an~~ iframe). ~~This this situation~~, when ~~the~~ SAML authentication ~~initiates~~, the identity provider page will ~~be opened into~~ a new browser window. While this window is ~~open~~, the embedded (original) window ~~shows an overlay that tells~~ the user that ~~the~~ authentication is in progress in ~~another browser~~ window. If ~~popups are blocked in~~ the ~~web~~ browser, a descriptive message ~~is shown to the user which asks~~ the user to disable ~~the~~ popup blocking, ~~or to click in~~ the ~~browser frame to~~ open the ~~popup~~ window. Once the identity provider login ~~has been completed successfully~~, the ~~popup~~ window will ~~be closed~~ and the original browser window will go to QPR ProcessAnalyzer. If the separate browser window is closed ~~prior to~~ completing the login, the original ~~browser~~ window will ~~show normal PA~~ login view ~~open~~.		When QPR ProcessAnalyzer is embedded into another website with the [[SAML_2.0_Federated_Authentication\|SAML authentication]] enabled, the authentication process is handled in a separate browser window or tab. This is necessary because some identity providers (IdP) do not permit authentication within an embedded frame (iframe element). Consequently, when SAML authentication begins, the identity provider's page will open in a new browser window. While this window is active, the embedded (original) window displays a message informing the user that authentication is in progress in a separate window.

			If the browser has popup blocking enabled, the new window cannot open. In such cases, a descriptive message prompts the user to disable popup blocking. Additionally, the user can manually open the authentication window by clicking the embedded frame, even if popups are blocked. Once the identity provider login is successful, the new window will close, and the original browser window will redirect to QPR ProcessAnalyzer. However, if the separate browser window is closed before completing the login, the original window will display the standard QPR ProcessAnalyzer login view.

Ollvihe at 20:08, 26 October 2025

2025-10-26T20:08:56Z

← Older revision		Revision as of 20:08, 26 October 2025
Line 22:		Line 22:

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

			== Using SAML authentication with embedding ==
			When QPR ProcessAnalyzer is embedded to another website and the [[SAML_2.0_Federated_Authentication\|SAML authentication]] is in use, the authentication is performed in a separate browser window or tab. This is because some identity providers don't allow the authentication to be performed in as embedded (in an iframe). This this situation, when the SAML authentication initiates, the identity provider page will be opened into a new browser window. While this window is open, the embedded (original) window shows an overlay that tells the user that the authentication is in progress in another browser window. If popups are blocked in the web browser, a descriptive message is shown to the user which asks the user to disable the popup blocking, or to click in the browser frame to open the popup window. Once the identity provider login has been completed successfully, the popup window will be closed and the original browser window will go to QPR ProcessAnalyzer. If the separate browser window is closed prior to completing the login, the original browser window will show normal PA login view open.

Ollvihe: Ollvihe moved page Website Embedding to Embed to Website without leaving a redirect

2025-09-17T22:38:18Z

Ollvihe moved page Website Embedding to Embed to Website without leaving a redirect

← Older revision	Revision as of 22:38, 17 September 2025
(No difference)

Ollvihe at 22:33, 17 September 2025

2025-09-17T22:33:41Z

← Older revision		Revision as of 22:33, 17 September 2025
Line 12:		Line 12:
	</html>		</html>
	</pre>		</pre>


	== Change CSP frame-ancestors setting ==		== Change CSP frame-ancestors setting ==
Line 19:		Line 18:
	frame-ancestors 'self' example.com;		frame-ancestors 'self' example.com;
	</pre>		</pre>

			If the CSP prevents the embedded website from showing, there will be a descriptive error message in the browser console. It contains details which CSP directive didn't allow to open the page.

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

Ollvihe at 22:32, 17 September 2025

2025-09-17T22:32:11Z

← Older revision		Revision as of 22:32, 17 September 2025
Line 1:		Line 1:
	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 [[QPR_ProcessAnalyzer_Security_Hardening#HTTP_Response_Headers\|Security Hardening]].		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 [[QPR_ProcessAnalyzer_Security_Hardening#HTTP_Response_Headers\|Security Hardening]].

			== Example webpage ==
			This is a simple example page containing an iframe element that embeds QPR ProcessAnalyzer.

			<pre>
			<!DOCTYPE html>
			<html>
			<body>
			<iframe src="https://processanalyzer.company.com/qprpa/ui/#/dashboard?sys:dashboardIdentifier=/MyProject/MyDashboard" height="600" width="900"></iframe>
			</body>
			</html>
			</pre>


	== Change CSP frame-ancestors setting ==		== Change CSP frame-ancestors setting ==

Ollvihe: /* Change CSP frame-ancestors setting */

2025-09-17T22:29:11Z

Change CSP frame-ancestors setting

← Older revision		Revision as of 22:29, 17 September 2025
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.