I have two users A and B. I want to grant B the permission to create, drop, etc. all tables in A's schema. As far as I can see, I can grant B full access to all schemas not a specific one. Is this correct?
3 Answers
You are correct that there is no way to grant a user create/drop/etc permissions on an entire schema. I suggest you look into proxy authentication. This basically involves altering user A to allow user B to proxy as A:
ALTER USER A GRANT CONNECT THROUGH B;
Then the connection uses user B's authentication, but gets the permissions of user A.
connect B[A]/Password@Database
This question was somewhat covered by my more specific question here.
Note on Roles: Roles work well for giving Object Privileges to another user since the privileges are tied to a specific object. While Roles can grant System Privileges, they apply either to the users own schema or to the entire database and therefore can't apply to another schema. For example, the user B could be granted CREATE TABLE
which would allow it to create tables in its own schema or CREATE ANY TABLE
which would allow it to create tables in any schema. These permissions could be granted directly or through a role, but the former wouldn't allow create privileges in the A schema. The latter would, but would also allow create privileges in any schema including sys, which would be a security concern.
-
Thanks for the answer. This is a pity of course. Basically, I don't understand why such a simple feature is not available in Oracle. Commented Feb 17, 2012 at 15:09
-
2Just found this feature on a 12c wish list: dadbm.com/2012/03/oracle-database-12c-wish-list Commented Aug 30, 2012 at 17:33
-
1I would highly prefer to decouple users from schemas. Just like in MySQL. Commented Aug 30, 2012 at 18:04
-
The permission would have to exist for the decoupling to work, so perhaps it would be a first step in that direction. Commented Aug 30, 2012 at 20:25
Just create a procedure on the target schema which involves EXECUTE_IMMEDIATE to create tables (check for other DDLs!!). Then grant the source schema privilege to execute on procedure. This should do the trick without security concerns.
You could just create a role with those permissions, and grant the role to whoever needs that ability.
-
How is that supposed to work? Leigh said that I cannot grant on an specfic entire schema. Commented Feb 17, 2012 at 15:29
-
1A Role can only include permissions that can be granted directly. The user B could be granted
CREATE TABLE
which would allow it to create tables in its own schema orCREATE ANY TABLE
which would allow it to create tables in any schema. These permissions could be granted directly or through a role, but the first is too narrow and the second too broad. Commented Feb 17, 2012 at 15:56 -