Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Differences Between Ticketing (Old) and Web Ticketing (New)

Hello QlikCommunity!

I have been doing a lot of reading on the new Web Ticketing Authentication process, but am still a little in the dark about the differences it has with the old Ticketing process.

If I understand correctly, Web Ticketing is designed primarily to pass to AccessPoint. However, can Web Ticketing still be used to pass users to the IE Plugin Client? Or even have both Ticketing and Web Ticketing enabled for different apps?

The reason I ask is because we are currently slowly migrating to using AJAX (AccessPoint). Many of our old applications will continue to use the IE Plugin (until we can transform them to work flawlessly in Ajax), while any new apps will be built for Ajax. We wanted to set up the security for Ajax apps and AccessPoint using Web Ticketing, but we didn't want to interfere with all of the work we have done for the old Ticketing system that is behind all of the IE Plugin apps.

Any knowledge or ideas would be greatly appreciated!

-Chris McPherson

1 Solution

Accepted Solutions
Not applicable
Author

I was able to publish two custom authentication procedures, one to route to the IE plugin version of the app, and another to route to the AJAX version of the app. I created a unique virtual directory in IIS to each of these authentication procedures. Now going forward I will have the new applications calling the AJAX authentication procedure and the old applications calling the IE plugin authentication procedure (the old apps are not yet ready for AJAX).

View solution in original post

3 Replies
jaimeaguilar
Partner - Specialist II
Partner - Specialist II

Hi,

you may want to take a look to this post:

An introduction to QlikView Security using Web Tickets

Regards

Not applicable
Author

Thank you for the reference Jaime.

I did run across this blog post in my readings yesterday and it certainly helped answer many of the questions I had regarding Web Ticketing. However, I am still unsure about what it would take to migrate from using the old Ticketing process (without loosing too much work) and/or the possibility of running both authentication processes (old and new) for their respective apps.

Any additional insight would be great!

-Chris McPherson

Not applicable
Author

I was able to publish two custom authentication procedures, one to route to the IE plugin version of the app, and another to route to the AJAX version of the app. I created a unique virtual directory in IIS to each of these authentication procedures. Now going forward I will have the new applications calling the AJAX authentication procedure and the old applications calling the IE plugin authentication procedure (the old apps are not yet ready for AJAX).