Re: Database Connection Filtering

Brian,

The intent here is to move some of the security policy enforcement out of the database and into the system. One would like it to be transparent to most of the many ways to connect to the database, which makes monitoring the listener ports the natural place to do it.

The question remains, though, whether that is a reasonable place to do it or even whether there is any place where it is feasible.

Brian Peasland <peasland_at_edcmail.cr.usgs.gov> wrote:

: You didn't explain why you want this setup. In some respects, SQL*Plus
: is doing the things that you are asking for. But if it is not meeting
: your needs, then you'll want to develop some middle tier (perhaps a Java
: Servlet) that will satisfy your requirements. 
 

:> Is something like this possible given the multitude of
:> driver setups?
:>
:> I would like to think that all interactions with the database
:> boil down to sql statements in ascii (or some public encoding
:> scheme) coming across one of the listener ports.
:> Is this a correct guess, or are things more complicated than that?
Received on Wed Jun 21 2000 - 00:00:00 CDT