Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 237
  • Last Modified:

Web Client Connection to Database

I am running a product call EMS Professional which is a room reservation system.  It is running on a Windows 2008 server with a Microsoft SQL Express 2008 database backend.  This product have a web client so that you can access the system from a web browser without the need for a client installed on the local machine.  My problem is that when a user logs into the system via the web client it takes up one of the concurrent user licenses for that system.  When the logoff it gives that license back.  If they close the browser or tab without logging off the system still keeps them logged in.  What can I do to either force their logoff when they close the tab or reduce the amount of time it takes for they system to kick them off when the close the browser or tab?

Any help is greatly appreciated.
0
cpelrod
Asked:
cpelrod
  • 4
  • 2
1 Solution
 
Ted BouskillSenior Software DeveloperCommented:
That is a design flaw because of the way web browsers work so the vendor should fix it as a bug.  Have you contacted the vendor to fix it?

Otherwise, if the product is running on IIS on the Windows box, you may be able to shorten the web session timeout, however, that would also meant that if a client didn't log out and left the client idle they could be timed out automatically.

Can you ask the vendor how to shorten the session timeout?  If not, then we can try and do it in IIS if that is hosting the web application.
0
 
cpelrodAuthor Commented:
IIS is hosting the web app.  The vendor says that the issue is an IIS issue and they don't do IIS support so it is up to me through IIS to resolve this if possible.  My current strategy has been to strong-arm the users into remembering to log-out.
0
 
Ted BouskillSenior Software DeveloperCommented:
Well the vendor is 100% wrong.  It's the way the internet was designed.  When a browser gets a copy of the page it disconnects from the server and there is no special event override that will trigger a call back when the user closes the browser.  It's NOT an IIS issue.

If you search this site I've answered the question of solving the log out issue when a browser closes many times and there is no solution.  The best you can do is a JavaScript trick to ping the server frequently with a very short session so the ping keeps the session alive.  If the ping disappears the session auto logs out the user.

However, let's not worry about arguing with the vendor who seems to have questionable knowledge.

OK, then is it an ASP.NET web application?  If it is then we can override the session timeout to make it shorter.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
cpelrodAuthor Commented:
I've requested that this question be deleted for the following reason:

I am worried I will break this application and have decided to leave it as is.
0
 
Ted BouskillSenior Software DeveloperCommented:
There is a fix that can be implemented without breaking the application and I am willing to work with the Asker to correct it.
0
 
Ted BouskillSenior Software DeveloperCommented:
#1 I give up, delete the question
0

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now