topic Re: Virtual Proxy Ticket Authentication causes error for default Proxy connection in Management & Governance

Virtual Proxy Ticket Authentication causes error for default Proxy connection

ygfletch — Sat, 16 Nov 2024 06:46:02 GMT

Hey all,

I have created a virtual proxy which uses the ticket method of authentication. I have this running on a Nodejs web server which is authenticating users fine, however this is triggered from an action in an app that is connected via the default proxy (ie no specified proxy). When the virtual proxy ticket gets the user authenticated it causes an error on the default proxy app the user has open. The error message they get is the "Connection to the Qlik Sense engine failed for unspecified reasons..." and the only thing they can do is click the refresh button.

Can anyone help? Are you allowed to be authenticated with the default proxy and a second virtual proxy at the same time?

Many thanks

Re: Virtual Proxy Ticket Authentication causes error for default Proxy connection

ganapati_h — Thu, 24 Jan 2019 13:56:07 GMT

Can you change the URL by appending proxy e.g https://servername/hub to https://servername/vproxy/hub and try.

Regards,
GH

Re: Virtual Proxy Ticket Authentication causes error for default Proxy connection

ygfletch — Thu, 24 Jan 2019 17:44:26 GMT

The URL that uses the virtual proxy has the prefix in, otherwise that wouldn’t work.

User is in the dashboard via url of server/Sense/app, they click a button that starts a Node server which takes the username and gets a ticket via the virtual proxy. Using this ticket the server starts a session using server/proxy/Sense/app which authenticates fine. However at this point the original dashboard the user is viewing errors, the one with server/Sense/app.

I want to use the two different proxies so the sessions and authentication methods are different.