Comprehensive Questions on Using qlik-embed with Cookie Authentication
Hello Qlik Community,
I have been working on integrating qlik-embed into an Angular 17+ application that currently utilizes the Capabilities API (via require.js) to connect to a self-hosted Qlik Sense server. Our backend authenticates against Qlik Sense and returns an authentication cookie that the frontend uses. However, I am facing challenges in implementing qlik-embed within this setup and have several questions I hope the community can help clarify.
Authentication Using Cookies:
In our current setup, the backend handles authentication and passes an auth cookie to the frontend. With qlik-embed, I couldn't find clear documentation on how to proceed with this approach.
The constructor for client-managed authentication was suggested (link), but how does this work in scenarios where a backend handles authentication and not the frontend directly?
We also use a proxy to manage HTTPS and WSS traffic, ensuring the Qlik Sense server remains private. Since qlik-embed requires data-host and data-login-uri to directly access the Qlik Sense server, is there a recommended way to further secure this setup?
Handling WebSocket Connections:
In our current implementation with the Capabilities API, we manage WebSocket (WSS) connections manually, allowing us to open and close connections as needed, particularly useful when handling multiple apps in a mashup.
With qlik-embed, how can we manage WebSocket connections efficiently? Is there an equivalent way to programmatically control when connections are opened and closed?
Event Handling in qlik-embed:
Using the Capabilities API, we can handle events such as session timeouts. However, I couldn't find documentation on handling similar events with qlik-embed.
How can we catch session expiration, connection failures, or other relevant events when using qlik-embed?
I appreciate any guidance or documentation that could help clarify these points. Thank you in advance for your support!
