Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Manikandan_PadmaNagarajan
Partner - Contributor II
Partner - Contributor II

Insight Adviser not responding outside the server

Insight Adviser is not working as expected outside the server using virtual proxy (SAML)

When using localhost - It is working fine.
Even while using virtual proxy with Windows authentication method, issue is not appearing.
Only when virtual proxy with SAML authentication method is used, issue appears 'No apps were found'

Any solution for the issue ? 

 

Qlik Insight Advisor  

1 Solution

Accepted Solutions
Manikandan_PadmaNagarajan
Partner - Contributor II
Partner - Contributor II
Author

This is the issue with QlikSense version, the virtual proxy of SAML is not identified the USERNAME and EMAIL ( Space and "@" symbols are converted into different code (+, 40 etc). The bug has been fixed in the Nov 2020 patch 4.

We have updated the Nov 2020 Patch 11 and the issue is resolved

View solution in original post

4 Replies
Anil_Babu_Samineni

Which version of Qlik sense you are using?

Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
Manikandan_PadmaNagarajan
Partner - Contributor II
Partner - Contributor II
Author

November 2020

 

Anil_Babu_Samineni

I identified with Feb 2021 same behaviour, It will improve in later stage. Here is the Bug ID If you are raising anything to Qlik (QB-4261)

Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
Manikandan_PadmaNagarajan
Partner - Contributor II
Partner - Contributor II
Author

This is the issue with QlikSense version, the virtual proxy of SAML is not identified the USERNAME and EMAIL ( Space and "@" symbols are converted into different code (+, 40 etc). The bug has been fixed in the Nov 2020 patch 4.

We have updated the Nov 2020 Patch 11 and the issue is resolved