Message-Id: <22528.293308@fatcity.com> From: "JOE TESTA" Date: Tue, 10 Sep 2002 10:54:02 -0400 Subject: methodology to keep only certain programs to connect to This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_B3EFFD9F.640530F0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I've been tasked to ensure only certain app programs access the database. I'm thinking on-logon trigger, check the program field from v$session. = unfortunately v$session is for all sessions, i can't seem to find the view = that tells me only MY info during login. I only want the sid, serial#, = username and program for my just now connection to the database. Does this exist or am I going about this the wrong way? We're thinking of checking those fields to make sure sql*plus, toad, etc = can't connect as a particular user(even though the password is known out = in the community). any ideas would be greatly appreciated. joe --=_B3EFFD9F.640530F0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML

I've been tasked to ensure only certain app programs access the=20 database.

I'm thinking on-logon trigger, check the program field from=20 v$session. unfortunately v$session is for all sessions, i can't seem = to=20 find the view that tells me only MY info during login. I only want = the=20 sid, serial#, username and program for my just now connection to the=20 database.

Does this exist or am I going about this the wrong way?

We're thinking of checking those fields to make sure sql*plus, toad, = etc=20 can't connect as a particular user(even though the password is known out = in the=20 community).

any ideas would be greatly appreciated.

joe