RE: Prevent connections for some users through SQL*Plus, TOAD
- From: Tanel Poder <tanel.poder.003@xxxxxxx>
- To: saints.richard@xxxxxxxxx, "'ORACLE-L'" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 02 Jun 2008 21:48:07 +0800
Raise an exception in that trigger and all users without "administer
database trigger" privilege can't connect anymore.
But if you need to do such things you should really review your security
policy - as if you enforce security by checking client executable name, then
anyone who can change client executable name (all users!) can work around
your policy.
--
Regards,
Tanel Poder
<http://blog.tanelpoder.com/> http://blog.tanelpoder.com
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Ricardo Santos
Sent: Monday, June 02, 2008 19:48
To: ORACLE-L
Subject: Prevent connections for some users through SQL*Plus, TOAD
Hello to you all,
I've an old fashion application that uses an Oracle Database where each
application user, is also a database user. That way, each user can connect
to the database through other tools beside the application, like TOAD,
SQL*Plus, etc.
Other related posts:
