Qlik Sense Enterprise returns error 400 Bad request with header authentication when addressed with DNS name

[Damien_V]

Qlik Sense Enterprise returns 400 Bad request errors when accessed using the DNS name and with header authentication implemented. 

The Qlik Sense Proxy service losgs (Trace/Audit_proxy) read:

1923969 20200420T092701.236+0100 WARN QlikServer1 Audit.Proxy.Proxy.Core.Connection.Validation.ConnectionDataValidator 37 2535c7fe-bf18-4abf-932f-06d11772f7f4 DOMAIN\qvservice Http request Host is not allowed: insights.domain.local.

Environments:

• Qlik Sense Enterprise for Windows November 2019 and later

Verify that the DNS name is added to the WebSocket origin white list in the virtual proxy. In earlier versions prior to November 2019, this list of allowed host names was only checked against for WebSocket connections. More recent versions also verify it for HTTP connections. 

For information on how to configure the WebSocket origin white list, see How to configure the WebSocket origin white list and best practices .

Please also note that the name should be added in the allowlist without the protocol. Such as:

Correct: insights.domain.local
Incorrect: https://insights.domain.local

[Farsana]

Hi, 

In Modheader the authentication was success, but in qlik cli  am getting Error: 400 - Bad Request - Qlik Sense, I am not sure when  the token was same in modheader and qlikcli its giving different ouput for JWT validation

when migrating from qliksense to cloud. 

Can i get some hints to trouble shoot the issue.