Re: methodology to keep only certain programs to connect to

I'm working with an application that uses a combination of encrypted seed numbers and password protected roles to limit access to the application tables to the specific application and version.

In this database, any external application (sqlplus, etc) cannot provide access to the application tables since that requires activation of the password protected role. The only default role for users is a connect role that has only connect privs. And, you can't just grab a copy of the application from anywhere and use it against the database since the encrypted seed number compiled into the application is checked against the value in the database before a connection is permitted.

Glenn Stauffer

On Tue, 2002-09-10 at 11:58, JOE TESTA wrote:
> 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.
Received on Tue Sep 10 2002 - 12:37:51 CDT