Troubleshooting Embedded Analytics

Q: If user in group A is responsible to create app and only allow to publish to only users within group A and we should want to embed it to a webpage. since we are using saml, users within group A accessing to the webpage will be able to see the app, but users that are not in group A will not be. For such case, what would be the recommended approach to allow the app to be embed webpage and allow all user to view the app?

A: Whether a user can see the embedded app/objects or not depends on if he has Read rights on the object as per the security rule and is not dependent on the type of authentication used.

Q: Does this apply to Qlik cloud as well?

A: For most parts yes, the front end code is nearly the same, but the configuration in the Qlik Cloud console requires additional steps.

Q: Any special considerations if running Qlik Sense behind a reverse proxy such as NGINX or an F5?

A: Make sure to indicate the URL the user access when accessing Qlik Sense (the reverse proxy URL and not the internal Qlik Sense URL). Also make sure to not alter headers used by the APIs.

Q: Is it possible to authenticate iframes with qlik Saas and, if so, how?

A: Yes, by using javascript to verify if the user is already authenticated or not and redirect to the login page if not.

Q: Is the nebula.js mashup available in Qlik Sense Client Managed?
A: Yes, it is.

Q: I am using Qlik Cloud. Is there any way to have anonymous access for embedded sheets and charts?

A: Unfortunately, it’s not possible at the moment.

Q: Is it possible to attach a chart by the id of the object regardless of the type of chart it is with nebula.js?

A: Only charts listed on the page of nebula.js supported charts can be used.

Q: What are the major differences between embedding with Qlik Sense Enterprise on Premise and Qlik Sense Cloud?

A: The setup to be done in the Qlik Management console (virtual proxy) and the setup to be done in the Qlik Sense cloud console (web integration and CSR) are different. Most of the front end code is the same.

Click here for video transcript

article Troubleshooting Embedded Analytics in Official Support Articles

Troubleshooting Embedded Analytics