Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Aurelien_Martinez
Partner - Specialist II
Partner - Specialist II

Qlik Sense Mashup - error 401 with internal_windows_authentication (qdt-components)

Hi,
I’m developing a mashup that connects to a Qlik app on a remote server.

I use qdt-components (https://github.com/qlik-demo-team/qdt-components) to connect to the app.

The mashup is hosted on localhost:4200.

 

I’m getting an error when I try to launch the mashup :

  • I first get prompted for credentials
  • I log in successfully
  • Then the app fails to load a file

 

Aurelien_Martinez_0-1695115577492.png

When the mashup tries to load /resources/qmfe/import-map.json, it is redirected to /internal_windows_authentication, which fails with a HTTP 401 error.

It’s weird that only this call fails, while the previous ones (/resources/js/qlik.js for example) complete successfully.

 

Do I need to configure something on the server ?

Thanks for your help

 

PS: We are in Qlik Sense August 2023 Patch1

Help users find answers! Don't forget to mark a solution that worked for you!
Labels (1)
  • API

1 Solution

Accepted Solutions
Damien_Villaret
Support
Support

Hello @Aurelien_Martinez 

I can indeed replicate the same behavior in August 2023. It has nothing to do with qdt components, it also happens with a simple mashup created from the devhub and then moved an external webserver (The issue will happen as long as the mashup is not hosted directly in Qlik Sense)

I see that Qlik R&D has already started to investigate this issue around 10 days ago (QB-21812), but there is no fix available yet.

I see that you have already opened a support case, which I linked to the defect in order to increase the weight and I have let the engineer in charge of your support case that this is already a known issue.

Best regards,

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

View solution in original post

6 Replies
Aurelien_Martinez
Partner - Specialist II
Partner - Specialist II
Author

The problem may be the august vesion, because the same code work on may 2023.

Help users find answers! Don't forget to mark a solution that worked for you!
Damien_Villaret
Support
Support

Hello @Aurelien_Martinez 

Indeed, that endpoint that is failing doesn't seem to exist in the May 2023 version. It could be it doesn't include credentials for cross-domain requests (The "allow-access-control-credentials" doesn't seem to be included on this request when I compare to other requests)
Does this cause any issue though? Is the mashup failing to load or it's just a harmless error showing the browser dev tools ?

If the issue is solved please mark the answer with Accept as Solution.
Aurelien_Martinez
Partner - Specialist II
Partner - Specialist II
Author

Hi,

 

Thanks for your answer. The mashup failing to load.

Help users find answers! Don't forget to mark a solution that worked for you!
Damien_Villaret
Support
Support

Hello @Aurelien_Martinez 

I can indeed replicate the same behavior in August 2023. It has nothing to do with qdt components, it also happens with a simple mashup created from the devhub and then moved an external webserver (The issue will happen as long as the mashup is not hosted directly in Qlik Sense)

I see that Qlik R&D has already started to investigate this issue around 10 days ago (QB-21812), but there is no fix available yet.

I see that you have already opened a support case, which I linked to the defect in order to increase the weight and I have let the engineer in charge of your support case that this is already a known issue.

Best regards,

If the issue is solved please mark the answer with Accept as Solution.
Aurelien_Martinez
Partner - Specialist II
Partner - Specialist II
Author

Hi,

Thanks for your time, I will wait the fix.

Best regards

 

 

Help users find answers! Don't forget to mark a solution that worked for you!
Skage
Partner - Contributor III
Partner - Contributor III

Hi @Damien_Villaret

could this be the reason why I get the same 401 for all @fontface-imports via the Sense-css-files when moving a Sense (Feb 2024)-hosted mashup to an external webserver?

/lars