import React from 'react'; import Link from '@mui/material/Link'; import Collapse from '@mui/material/Collapse'; import Typography from '@mui/material/Typography'; const ConnectionGuid = ({ showGuid }) => ( WebSocket URL The development server needs to connect to and communicate with the Qlik Associative Engine running within any of Qlik's product offerings. The connection is done through the WebSocket protocol using a WebSocket URL format that differs slightly between products. Enter the WebSocket URL that corresponds to the Qlik product you are using. Qlik Cloud Services Web integration id format: There are two ways in order to connect through WebSocket:
1. qlik-web-integration-id
2. qlik-client-id

Web integration id:
wss://<tenant>.<region>.qlikcloud.com?qlik-web-integration-id=<web-integration-id>
Example: wss://qlik.eu.qlikcloud.com?qlik-web-integration-id=xxx

For more info, visit{' '} Managing web integrations .
OAuth Client ID URL format:
wss://<tenant>.<region>.qlikcloud.com?qlik-client-id=<client-id>
Example: wss://qlik.eu.qlikcloud.com?qlik-client-id=xxx
Redirect URL form: http://localhost:8000/auth/login/callback
The qlik-web-integration-id OR qlik-client-id must be present in order for QCS to confirm that the request originates from a whitelisted domain.

Qlik Sense on Windows WebSocket URL format: wss://<sense-host.com>/<virtual-proxy-prefix>
Example: wss://mycompany.com/bi

Note that for the Qlik Sense Proxy to allow sessions from this webpage, {window.location.host} needs to be whitelisted in QMC in your Qlik Sense on Windows deployment. In addition, you need to enable Has secure attribute and set SameSite attribute to None.
Also some "Additional reponse headers" needs to align with the whitelisted domain: Make sure you are logged in to Qlik Sense in another browser tab.
Qlik Sense Desktop WebSocket URL format: ws://localhost:4848
); export default ConnectionGuid;