Database access restiriction.

Hi, I am charge of system administration of one of v7.3 Informix database server working on sun solaris 2.6. We are currently developing an ODBC application where Visual Basic is used as the client development environment. The application developed ODBC connection in order to access and retreive data from SUN SERVER. It obtaines the username and password from the user and connects to Informix via ODBC. The application will be distrubuted to several users in our department. Each user may have their own accounts to access the server. ( Accounts will be created on SUN Server.) However, we want to setup a security system in order to restrict the access of the user to the database. We don't want for a user to connect two times using different worksation. As a summary, each user shouldn't connect two times using the same application. And also we want for each user to have inactivity timeout. When it finishes it's maximum idle time, the database server must refuses the odbc requests. Any information related with the above situation will be applicable. Thanks in advance, Yener KILIC Sent via Deja.com http://www.deja.com/ Before you buy.

yener@my-deja.com wrote: > > Hi, > > I am charge of system administration of one of v7.3 Informix database > server working on sun solaris 2.6. We are currently developing an ODBC > application where Visual Basic is used as the client development > environment. > > The application developed ODBC connection in order to access and > retreive data from SUN SERVER. It obtaines the username and password > from the user and connects to Informix via ODBC. The application will > be distrubuted to several users in our department. Each user may have > their own accounts to access the server. ( Accounts will be created on > SUN Server.) > > However, we want to setup a security system in order to restrict the > access of the user to the database. We don't want for a user to connect > two times using different worksation. As a summary, each user shouldn't > connect two times using the same application. And also we want for each The only way I see to do this is to use some ODBC middleware that will allow you to restrict users to one login. Look at some of the middleware servers out there. > user to have inactivity timeout. When it finishes it's maximum idle > time, the database server must refuses the odbc requests. Any > information related with the above situation will be applicable. I'd do this one in the application as a timer callback. You just disable the timer when the users starts a request and reset the timer each time a request completes. If the timer goes off disconnect from the server. Art S. Kagel Art S. Kagel