Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

After Timeout, SSO Login Page is Not Displayed

We have started using an SSO package to authenticate users, our webserver is IIS. User ID is provided in HTTP headers.

When a user has a QliKView application open for over 30 minutes unattended, when they return they can often find the dashboard freezes.

Using the Fiddler application I can see that our SSO system recognises authentication session timeout and is sending an http response containing the HTML of it's login page. It seems to me that the QVA AJAX application is not expecting that HTTP response and does not handle it well, it is only expecting an HTTP response from the QVS. The SSO login page does not get displayed.

Sometimes pressing f5 for browser refresh will solve the issue, sometimes not.
Users of Firefox often find a pop displaying "Network Error" in addition to the QV application freezing.
If a user session is left on the AccessPoint menu page and they return after 30 minutes trey are always redirected succesfully to the SSO login page.

Our SSO inactivity timeout is 30 minutes.
For QlikView Web Server config.xml
QvsTimeout is 1800 seconds
SessionCookieTimeout is 30 minutes

Does anyone else encounter this
Does anyone have an answer / workaround?

4 Replies
Chanty4u
MVP
MVP

Bill_Britt
Former Employee
Former Employee

Hi,

I would contact SiteMinder to see if they can help you with the redirect that is needed. The cookie has expired and so the login information is invalid.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
Anonymous
Not applicable
Author

The SSO system is not a commercial one. It uses an ISAPI filter in IIS to redirect to the SSO.

When a user interacts with the dashbaord after being away for 30 mins+ the QlikView Ajax application (QVA) will be sending an http with ajax content.


IIS/ISAPI is recognising the authentication cookie timeout and redirecting to SSO.


SSO is providing an http response containing the html of the login page.


It seems to me that QVA is expecting an http response containing ajax data and when it gets html from the SSO instead it doesn't know what to do with it. It should just display it?

Bill_Britt
Former Employee
Former Employee

Hi Paul,

Take a look at this and see if this helps. If not, contact your account manager and I am sure he can find someone in Consulting Services to help you.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.