Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
morenoju
Partner - Specialist
Partner - Specialist

SAML Authentication - Error 400

I've configured a client in Keycloak and a new virtual proxy in Qlik Sense Enterprise to make use of SAML Authentication.

When trying to access https://myserver/keycloak/hub I get an Error 400 Bad Request The http request header is incorrect.

morenoju_0-1654024038929.png

I'm assuming there must be something wrong in my Virtual Proxy configuration. Any idea though? My current configuration:

morenoju_1-1654024112360.png

 

 

Labels (1)
2 Solutions

Accepted Solutions
Francisco_Fernandez

Hello @morenoju ,

The v.proxy config looks fine, the problem must be somewhere else.

I would suggest you to check this article:

https://community.qlik.com/t5/Knowledge/Qlik-Sense-Common-error-messages-when-using-SAML/ta-p/171033...

and check the proxy logs trace logs: C:\Programdata\Qlik\Sense\log\Proxy\Trace

 

hope this helps.

 

Best regards,

Francisco

View solution in original post

morenoju
Partner - Specialist
Partner - Specialist
Author

Thanks @Francisco_Fernandez. The proxy trace log was being actually a bit misleading because it said "Http request Host is not allowed" which made me think that I had an issue in the white list of the virtual proxy.

However, I've just noticed that I never linked the virtual proxy to the Central proxy. Once I've done that, I've been redirected to the keycloak page.

View solution in original post

2 Replies
Francisco_Fernandez

Hello @morenoju ,

The v.proxy config looks fine, the problem must be somewhere else.

I would suggest you to check this article:

https://community.qlik.com/t5/Knowledge/Qlik-Sense-Common-error-messages-when-using-SAML/ta-p/171033...

and check the proxy logs trace logs: C:\Programdata\Qlik\Sense\log\Proxy\Trace

 

hope this helps.

 

Best regards,

Francisco

morenoju
Partner - Specialist
Partner - Specialist
Author

Thanks @Francisco_Fernandez. The proxy trace log was being actually a bit misleading because it said "Http request Host is not allowed" which made me think that I had an issue in the white list of the virtual proxy.

However, I've just noticed that I never linked the virtual proxy to the Central proxy. Once I've done that, I've been redirected to the keycloak page.