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: 
Martin22
Partner - Contributor III
Partner - Contributor III

SAML Change port

Hi,

I'm trying to implement SAML on our Qlik Sense platform (I made another post, on another problem we had with the certificate), and we have reached a point where we are getting the following error :

Error 400 - Bad request Contact your system administrator. The user cannot be authenticated by the SAML response through the following virtual proxy

 

I saw there was a post on this : https://community.qlik.com/t5/Knowledge/Error-400-Bad-request-Contact-your-system-administrator-The-... and it seems my problem comes indeed from the port, since I can see the 443 port in the metadata.

My question is : if the solution is to change the port from 443 to 1443, do we have to change it only in the metadata file, or do we have to also make the change somewhere in the QMC ? At the "Service listen port HTTPS (default)" of the central proxy, or in the URI to use in the virtual proxy for example ?

Regards,

Martin.

1 Solution

Accepted Solutions
Damien_V
Support
Support

Please check this article 

https://community.qlik.com/t5/Archived-Technical-Documents/Qlik-Sense-SAML-GET-request-invalid-forma...

 

Best regards,

If the issue is solved please mark the answer with Accept as Solution.

View solution in original post

8 Replies
Damien_V
Support
Support

Hi,

That is only one of the many possible scenario where error 400 can happen (this is a generic error)
You would need to check the Qlik Proxy logs for the same timestamp to know what happened.

https://community.qlik.com/t5/Knowledge/Qlik-Sense-Information-needed-to-Troubleshoot-SAML-SSO-relat...

https://community.qlik.com/t5/Techspert-Talks/STT-Integrating-SAML-with-Qlik-Sense-Enterprise/td-p/1...

 

If the issue is solved please mark the answer with Accept as Solution.
Martin22
Partner - Contributor III
Partner - Contributor III
Author

Hi,

Thank you for your answer.

I did check the logs, and there is an error message : SAML GET request invalid format 0

I didn't get a lot of information on it however, while the Error 400 post seemed to correspond, since I had the 443 port in the metadata. But it seems curious that we would change the extracted metadata without changing the platform it comes from, hence my question.

Is there any specific change to make regarding the error in the logs ?

Regards,

Martin.

Damien_V
Support
Support

Please check this article 

https://community.qlik.com/t5/Archived-Technical-Documents/Qlik-Sense-SAML-GET-request-invalid-forma...

 

Best regards,

If the issue is solved please mark the answer with Accept as Solution.
Martin22
Partner - Contributor III
Partner - Contributor III
Author

Thank you for the link,

The problem is I already tried it when first I saw the error in the logs, but I get redirected to an "Access Denied" page, with the message :

The content you are looking for has been archived or you may not have permission to this area. For assistance, private message @Sue_Macaluso or @Jamie_Gregory

Is there another support page on this subject ?

Sue_Macaluso
Community Manager
Community Manager

@Martin22 That document link is archived and why you cannot reach it. @Damien_V Do you have a new link to that information? or was it meant to come out of the archive?

Sue

Sue Macaluso
Damien_V
Support
Support

@Sue_Macaluso This shouldn't have been archived, that is still very valid for the current Qlik Sense versions.

If the issue is solved please mark the answer with Accept as Solution.
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Martin22 

The article was pulled out of the archive. Thank you, @Damien_V, for reviewing it and clearing it!

Don't forget to Like posts and use the "Accept as Solution" button on content that answered your question! Thanks 🙂
Martin22
Partner - Contributor III
Partner - Contributor III
Author

Hi,

It took us some time, but we finally succeeded in implementing SAML on our platform.

Thank you for your help, your responsiveness helped a lot.

Regards,

Martin.