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...