Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
April 13–15 - Dare to Unleash a New Professional You at Qlik Connect 2026: Register Now!
cancel
Showing results for 
Search instead for 
Did you mean: 
Kaushik2020
Creator III
Creator III

External URL issues

Dear All, 

We have an external URL using which the end users can access Qlik Sense from outside network. 

https://Qlikbi.external.in

Now issues what i am seeing. 

1. Allocate and deallocate is not showing in QMC. when we logout and login it show the new users. 

2. Created apps via External URL is not showing in Qlik Sense when we access QS inside the server.

3. When i stopped services, the external URL was working as usual. 

4. Users created on the server internally are not being authenticated to QS from the external URL.

Pls suggest what might be the issue for these.

 

Thanks in advance.

Labels (2)
1 Reply
RafaelBarrios
Partner - Specialist
Partner - Specialist

Hi @Kaushik2020 

it seems to me that you are pointing to different virtual proxies when accesing externaly and internally and that each virtual proxy authenticates with different users.

That would explain why what you create externally isn't visible internally, and it would also explain why you don't see the licenses; it treats them as two different users with different permissions.

Check the following

1. Create one app with the internal URL and another with the external URL, and look at the owners of both applications; you should have something like this.

RafaelBarrios_2-1767620278130.png

 

2. In my setup I have something similar; there are two users with the same userid but from two different domains.

RafaelBarrios_3-1767620352939.png

 

if this happens, my guess is that one of the virtual proxies is using windows authentication (by default)

https://my-internal-url/

and externally, https://Qlikbi.external.in is pointing to something like https://my-internal-url/SAML

 

Hope this helps.

Best,

Help users find answers! Don't forget to mark a solution that worked for you & to smash the like button! 🙂