Re: hot to limit sqlldr ?
Date: Wed, 13 Apr 2005 16:36:40 +0200
Message-ID: <d3jar7$c2d$1_at_inews.gazeta.pl>
Użytkownik Stefan napisał:
> ideally you are correct - however, I am hosting an application which
> requires that the application level user have the same username and
> password as the database level user, AND the database level user has to
> have insert/update/delete in order to be able to use the application's
> front end....
> I know it's a horrible design, but that's the way it is....
> so the only thing I've been able to think of so far is to create a
> LOGON trigger which kills sessions unless they are made via the
> appropriate client application...
> was wondering if there are any other ideas out there...
>
I know one. Change application ON_LOGON trigger.
Lest say application uses user SCOTT with TIGER password.
But real password is IGER and ON_LOGON trigger adds T.
You say user to logon SCOTT/TIGER, but if he uses sqlldr he just won't
connect.
(for example i just put 'T', you could think of more complex procedure).
-- NoelReceived on Wed Apr 13 2005 - 16:36:40 CEST