QS Web Ticketing Session

[van_nanney]

I have used web ticketing numerous times with older versions of QS and QV.  However on upgrading to June 2020 path 3 - I cannot get the ticketing to function as expected.  The C# code (same as what was used on previous sense servers successfully)  is able to successfully retrieve a ticket however when I use the ticket to launch to a resource like: 

https://[qlikserver]/[virtualproxy]/[resourcepath]&qlikTicket=ABC123456789

It will request windows AD login - since the virtual proxy does not have a "authentication module redirect URL" parameter.

If I provide a RedirectURI in the virtual proxy it will attempt to callback for authentication and will be stuck in a infinite authorization loop. 

In our setup all user information is passed via the ticket, thus no UDC actually exists.  When I setup a UDC with a user and attempt the calls above for that user, I get the same results.

It appears my ticket calls are not creating a session.   I have skipped over many versions of QS using ticketing,  is retrieving a ticket by external portal and launching Qlik Sense resources not supported in this workflow any longer???  Not sure where to look - any help is appreciated.

[Bastien_Laugiero]

Hello,

The described workflow should still work. I have found one article referring to a known issue with ticketing and Qlik Sense June 2020. Can you check if it may apply: https://support.qlik.com/articles/000108518

Also you might want to try with a simple powershell script and make sure it works as expected:

https://community.qlik.com/t5/Support-Knowledge-Base/Qlik-Sense-Generate-a-ticket-with-Qlik-proxy-AP...

Hope this helps!

[van_nanney]

Thank you for your reply.   I do not believe the issue per support article 000108518  applies to my scenario.  I was able to get my code working, just not in the scenario I described originally.  Interesting enough, the example you linked to follows the same scenario in how my "working" version is setup.   For years I have used ticketing with QlikView and QlikSense in the form of:

1. Call the Qlik QPS with userdir and userid and get a ticket
2. Append the ticket to the Qlik resource URL  "https://qlikserver/myqlikresource&qlikTicket=ABC

Apparently this flow is no longer supported - even though I cannot find any Qlik doc that say that is true.  I have tried this against 3 different QlikSense installs (all same version) all produce the same failed results.

However I can restructure the calls to workflow:

1. Setup the virtual proxy "authentication module callback URI"
2. Call Qlik with path to the resource I am trying to reach
3. Receive the auth callback
4. Call Qlik QPS with info from callback to get a ticket
5. Redirect to Qlik resource with ticket "https://qlikserver/myqlikresource&qlikTicket=ABC

This workflow functions correctly, creates a session and displays the resource. However results in rather convoluted code and extra knowledge of "how" all this works for any developers trying to maintain my code in future. 

I do appreciate your feedback.