Issue and Solution for SSO Integration between Qlik Sense Enterprise and Qlik Alerting (On-Premise)

[zolbae]

Hello,
I encountered an issue while configuring SSO integration between Qlik Sense on-premise and Qlik Alerting by following the official guide. I wanted to share my experience and solution with the community.

Version Infomation.

Qlik Alerting : 2024 November SR1

Qlik Sense Enterprise : 2023 May Patch16

---

Issue Description:

Here are the steps I followed for SSO integration:

1. Qlik Alerting Configuration:
   Entered the Qlik Sense server information in the Qlik Alerting settings.

   

2. HTML Integration Module Upload:
   Uploaded the HTML integration module (provided during the Qlik Alerting installation) to the Qlik Sense content library.

   

3. URL Access Setup:
   Added the URL pointing to the uploaded HTML file in the Qlik Alerting settings.

   
   

4. SSO Verification Process:

   • Qlik Alerting attempts to access the provided URL.
   • Since the HTML file is located in the Qlik Sense content library, a login to Qlik Sense is required for access.
   • During this process, the HTML file executes a script, receives parameters from Alerting, and finalizes the SSO connection.

---

Issue Faced:

Despite following the official guide, the following issue occurred:

• An error message appeared stating that there was an issue with the SSO file linked to the URL, and the integration failed. (Invalid SSO URL. Please contact your administrator.)
  

Root Cause Analysis:

• The JavaScript code inside the HTML file was obfuscated, making it difficult to analyze.
• After de-obfuscating the code, I identified the following problem:
  • The typical Qlik Sense URL structure is:
    https://qlikdomain.com:<port>/virtualproxy/
    However, since the HTML file is uploaded to the content library, its URL appears as:
    https://qlikdomain.com:<port>/virtualproxy/content/
  • In the JavaScript code, there is a function responsible for extracting the virtual proxy prefix by identifying /content in the URL and taking the preceding string.
    
    

• However, the de-obfuscated code revealed that it was hardcoded to search for /sense instead of /content.
• /sense is typically used as a prefix for single-configuration mashups but is not mentioned in the official guide for this integration.

---

Solution:

• I modified the JavaScript code to look for /content instead of /sense.
  

• After this change, the SSO integration worked perfectly without any issues.
  

---

Concerns and Questions:

• Although the solution worked, I am unsure why the JavaScript was hardcoded to look for /sense when the official guide suggests using /content.
• I am curious to know if anyone else has encountered this issue or if there is a better approach to solving it.

Questions:

1. Is modifying the JavaScript the correct way to solve this issue?
2. Has anyone else faced a similar issue with Qlik Alerting and Qlik Sense SSO integration?
3. If there are alternative solutions or best practices, please share them!

---

Conclusion:

I hope this helps others who might be facing a similar issue. If you have experienced this or have any insights, I would appreciate your feedback!
Thank you!

Qlik Sense Enterprise on Windows Qlik Alerting

[Frank_S]

Hello @zolbae 

Thank you for going above and beyond to share your solution.

If you wish, please consider posting this here in our Qlik Member Articles 

https://community.qlik.com/t5/Member-Articles/tkb-p/qlik-communityarticles

Kind regards...

[korsikov]

I have the same problem 

Qlik Sense May 2025 patch 3
qlik Alerting November 2024 SR2

@zolbae  can you share modifyed html file? 

[zolbae]

I will email you. Can I get your email address?

you can send a private message

[korsikov]

@zolbaeHUGE Thanks again — your input was absolutely essential.

Let me quickly summarize the key steps that solved the issue:

1. Enabling websocketEnable: true in .\config\default.json — which, while clearly documented at the beginning of the setup guide, is not mentioned in the Source configuration section — and I simply overlooked it.

2. And most importantly, setting the Alias Hostname field properly in Source