RE: Authorete
- From: "Jacques Kilchoer" <Jacques.Kilchoer@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 11 Mar 2004 14:35:55 -0800
The "set current_schema" option was not for security reasons but to eliminate
the need for the creation of all those synonyms.
-----Original Message-----
April Wells
no, I don't think that will give me what I'm really after...
The idea is to tie the hands of the programmers to such an extent that I KNOW
what they can and can not do... and how bad they can put me in a bind.
-----Original Message-----
From: Jacques Kilchoer [mailto:Jacques.Kilchoer@xxxxxxxxx]
Would it also work to create a logon trigger that does an "alter session set
current_schema = " instead of creating synonyms?
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On
Behalf Of April Wells
Ended up having to create case sensitive synonyms (upper case version, lower
case version) on the double quoted table structures or the user couldn't log
in.
Granting is easy... aliasing is the interesting part.
Try create synonym user on whoever.user
Oracle tends to get testy.
-----Original Message-----
From: Richard Stevenson
I guess dump software from vendors that don't understand reserved words
wouldn't cut it?
Seriously, wouldn't granting all privileges on the objects to another
user work ?
----- Original Message -----
From: April Wells < <mailto:AWells@xxxxxxxxxx> mailto:AWells@xxxxxxxxxx>
Has anyone worked with Authorete software against an Oracle database
before?
I am trying (silly me) to impose some security on this product, and they
have tables called... user... privilege... group... session... and I
need to have the tables owned by one user while another user can SUID
the data, but not affect the table structure (got burned on financials
implementation with customizations... ) and it is geeking out when the
user tries to log into the front end...
Other related posts:
