Message-Id: <22528.293320@fatcity.com> From: "Fink, Dan" Date: Tue, 10 Sep 2002 09:50:30 -0600 Subject: RE: methodology to keep only certain programs to connect to This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C258E1.CA348280 Content-Type: text/plain; charset="iso-8859-1" Can you use the USERENV or SYS_CONTEXT function? -----Original Message----- From: JOE TESTA [mailto:JTESTA@longaberger.com] Sent: Tuesday, September 10, 2002 9:58 AM To: Multiple recipients of list ORACLE-L Subject: methodology to keep only certain programs to connect to 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 ------_=_NextPart_001_01C258E1.CA348280 Content-Type: text/html; charset="iso-8859-1"

Can you use the USERENV or SYS_CONTEXT function?

-----Original Message-----
From: JOE TESTA [mailto:JTESTA@longaberger.com]
Sent: Tuesday, September 10, 2002 9:58 AM
To: Multiple recipients of list ORACLE-L
Subject: methodology to keep only certain programs to connect to

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