Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

How to configure the WebSocket origin allow list and best practices

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

How to configure the WebSocket origin allow list and best practices

Last Update:

Nov 1, 2022 8:44:33 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 18, 2019 5:23:43 AM

The WebSocket origin Allow List grants access to the hub from aliases and redirected addresses. This article explains how to configure the list and includes general DOs and DONTs.

 

To configure the WebSocket origin allow list:

  1. Open the Qlik Sense Management Console
  2. Navigate to Virtual Proxies

    virtual proxies 01.png

  3. Select the Virtual Proxy you wish to modify
  4. Double click the Virtual Proxy or choose Edit

    virtual proxies 02.png

  5. Expand the Properties menu by selecting Advanced
  6. Scroll down to locate the Host allow list 
  7. Modify the list accordingly and click Apply

    virtual proxies 03.png

 

 

Best Practices

Valid entries:

Incorrect entries:

  • .domain.com
  • *.domain.com

 

Related Content:

"An error occurred Connection lost" or "Bad Request the http header is incorrect on Qlik Sense Hub" 
Invalid entries in the Qlik Sense host allow list on the virtual proxy configuration 

Labels (2)
Comments
Ken_T
Specialist
Specialist

would this allow one environment to have mashups that can get js and css resources from another environment?  example, we have an enterprise (soon to be saas, maybe) and a QAP.  2 different environments.... we develop mashups locally and and have to point to resources on the enterprise system with an absolute URL (soon to be saas maybe).   can we whitelist things so that the QAP mashup can use css and js from another environment?  so we don't have to edit the mashup for deployment to QAP, which we use for public deployment.   we will be testing this soon, and I am not sure if it is a common scenario or not.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello Ken,

I think it may be best if you posted this question over in our Qlik Sense Integration forum to connect with users and active support engineers about it. The topic is a bit too complex to cover in an article discussion.

All the best,

Sonja 

fatinfazrizanor
Partner - Contributor III
Partner - Contributor III

Hi i have put the domain.com, and when i open the hub via the new url, it have the authentication login page as normal. But when i login, i cannot access with no error. the log in page keep appearing as it did not recognize my id.
I can login only if i use the original url.
Can you help what is the real problem?

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @fatinfazrizanor 

Changing the WebSocket Allow List will not affect authentication, and there may be something else at work here. I would suggest posting about your issue in our active Deployment & Management forum.

In the meantime, this might help: Problem logging in to QlikSense on the server using the dns-name & Cert question 

All the best,
Sonja 

SGMarquez
Contributor II
Contributor II

Gracias por las informaciones, el problema lo tenemos al acceder desde el sistema operativo de windows, si accedemos desde un ordenador Mac , movil iphone y un movil android si te permite, solo hay problemas con windows.

Version history
Last update:
‎2022-11-01 08:44 AM
Updated by: