Question

Connector Search and Session Cap

Connector Web Client

Updated January 5, 2016

asked on September 23, 2015

We have tested integrating some of our legacy applications with Laserfiche WebAccess, using the search action in the Connector profile. The integration works great, but we have noticed that if the browser is closed after each Connector search, the ninth search will result in an error message stating “No license has been allocated for this user. [9520].” Looking in licensing manager, it is apparent that the server is hanging on to the previous eight sessions and that an eight-session cap per for a single user is being enforced. This is only a problem if the browser (both Chrome or IE) is closed after each search. If the browser remains open, the existing session is reused and a cap is never reached. Is there any way around this other than instructing users not to close their browsers?

The same topic is discussed here and the proposed solution is to kill the session upon close of the browser. I think that would also solve my problem.

http://forums.asp.net/t/1120750.aspx?Kill+session+when+we+try+to+close+the+browser+without+logging+out+in+all+possible+ways

0 0

Answer

SELECTED ANSWER

replied on September 24, 2015

Hi Ryland,

You are correct that the error your seeing is related to the sessions not being disposed when a user closes their browser window. Unfortunately, as the link you posted points out, there is no good way to implement that functionality, since Http is stateless.

The solution is for users to either not close the tab in between running searches with Connector, or for users to click 'logout' in Web Access before closing the browser.

It's worth pointing out that while the session is not disposed on closing the browser, it will still timeout from inactivity. One possible way to mitigate the issue is to reduce the timeout period. That way, sessions will timeout faster and you'll be less likely to hit the 8 session cap between running searches with Connector. You can find instructions on configuring the timeout period here.

0 0

Replies

replied on September 25, 2015

Thanks Ryan. I also noticed the desktop client is not affected by this. and most of our heavier users are already using the desktop client.

1 0

replied on December 30, 2015

I finally got around to testing a change to the session timeout. While it does have the desired effect of minimizing the probability that a single user will hit the 8 session cap between running Connector searches, it also displays the "A timeout condition was detected . . . " message from within WebAccess. While this message is currently showing up for users with 30 minutes of inactive, the suggested change would make this popup after only 1 minute of inactivity. This would probably become contusing and/or annoying to users. Any other thoughts/workarounds for this?

0 0

replied on January 5, 2016

I suggest playing with the timeout period a bit more. It doesn't have to be 1 minute or 30 minutes. You can choose any period in between as well.

I think this is going to be one of those cases where there isn't a perfect solution. There's a trade-off between avoiding the session cap and timing out too quickly. Maybe something like 5 minute or 10 minute timeout period would best suit your use case.

It's also worth point out that, to the extent you can, training your users to click 'logout' will help alleviate this issue a lot.

0 0

You are not allowed to follow up in this post.

Question

Question

Connector Search and Session Cap

Answer

Replies

Sign in to reply to this post.