Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
MirelaPopovici
Partner - Contributor
Partner - Contributor

Socket Closed with Enigma

We have a bit of code in javascript using the enigma engine to obtain the first sheet id of an app. It works well in many of the installations.

However, on one environment it fails with a socket closed exception. with a hardcoded sheet id the graphics load and all of the rest apis work as well.

The problem occurs when trying to instantiate the enigma engine in this bit of code:

async function createEnigmaAppSession(schema, appId, identity, params) {
const session = enigma.create({
schema,
url: `wss://${TENANT}/app/${appId}/identity/${identity}?${params}`
});

handleDisconnect(session);

const enigmaGlobal = await session.open();
const enigmaApp = await enigmaGlobal.openDoc(appId);
return [session, enigmaApp];
}

I have triple checked the Content Security Policy with the server name and frameAncestors checked. the web integration id and api key and the private key seems to be ok.

MirelaPopovici_0-1740172787403.png

 

MirelaPopovici_1-1740172838988.png

 

Labels (3)
0 Replies