Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Qlik Sense: Cross-Origin Read Blocking (CORB) when using SAML authentication in a mashup

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Damien_Villaret
Support
Support

Qlik Sense: Cross-Origin Read Blocking (CORB) when using SAML authentication in a mashup

Last Update:

Oct 21, 2021 9:40:50 AM

Updated By:

Damien_Villaret

Created date:

May 14, 2019 6:22:39 AM

The browser is sending a Cross-Origin Read Blocking (CORB) when using SAML authentication in a mashup.

 

Environments:

Qlik Sense Enterprise on Windows 

 

Cause:

This is working as designed. A feature request has been created but nothing is currently planned on the roadmap.

When the SAML server responds with a login-HTML page, browsers will generally not accept this and will throw a CORB exception. If a login page is presented to the user from the SAML service it could not be displayed in a script reference anyway, even if it was accepted by the browser.

To facilitate this behaviour via a code change one would need to be able to configure virtual proxies to redirect the user to a general URL after the user has been authenticated in Qlik Sense. Here we are talking about a brand new feature, which would take more engineering time to implement and Product Management would need to be contacted for decision and prioritization about such feature request.

 

Resolution


The current way to accomplish this scenario is to use the "Stub page" method described in below article:

https://community.qlik.com/t5/Knowledge/Qlik-Sense-on-Windows-How-to-use-mashups-with-SAML/ta-p/1758...

 

Labels (1)
Version history
Last update:
‎2021-10-21 09:40 AM
Updated by: