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

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more

Qlik Sense: How to make a virtual proxy else than Central Proxy the default

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Damien_V
Support
Support

Qlik Sense: How to make a virtual proxy else than Central Proxy the default

Last Update:

Jul 15, 2021 3:39:54 AM

Updated By:

Sonja_Bauernfeind

Created date:

Dec 11, 2018 10:19:12 AM

The central proxy virtual proxy cannot be deleted and virtual proxy prefix are unique per proxy.

 

Environments:

 

Resolution:


In order to change to remove the prefix for a different virtual proxy to use another authentication method by default:

  1. in the QMC, go to "Virtual proxies" > "Central proxy (default)"
  2. Modify the virtual proxy prefix to the desired string
  3. Click "Apply" in order to save
  4. Go back to "Virtual proxies", double-click on the virtual proxy that you want to make default in order to edit it.
  5. Remove the virtual proxy prefix
  6. Click "Apply" in order to save


Note: If the virtual proxy made default is using SAML authentication, the SAML Assertion Consumer Service URL will also need to be updated in the Identity Provider configuration.

Labels (1)
Comments
Skage
Partner - Creator
Partner - Creator

Hi,

 

This isn't working for me.
I have an environment with two machines where we configured oidc-authentication by adding a new v-proxy with a prefix. It will load balance to both machines and is linked to both proxy-services. All three v-proxies have unique cookie names.

 

When adding a prefix to the two initial default v-proxies and removing the prefix from the newly created oidc-v-proxy the checkmark for "default" is checked and dimmed. The v-proxy overview is also showing Yes for the initial default and No for the v-proxy w.o. a prefix. The dimmed checkbox indicate that it has a function but it can't be unchecked and it is missing for any new v-proxy.
Bug or WAD?

/lars

ilyas393
Creator
Creator

Hi,

This isn't working for me either.

I add a prefix to the default proxy, updated session cookie header name and the description on the default proxy.

Then created another Virtual proxy using SAML authentication, kept the prefix empty.

I have tried restarting the services and still no luck. 

I am attaching a snapshot.

Any tip on how to switch the default NTLM based authentication virtual proxy to a SAML based authentication virtual proxy ?

 

ilyas393_0-1749601133488.png

 

Contributors
Version history
Last update:
‎2021-07-15 03:39 AM
Updated by: