• Authorization via Grant
syntax:GRANT object_priv[(columns)][on object] to {user|role|public} [with GRANT OPTION]
• Recycling through revoke
syntax:REVOKE object_priv[(columns)][on object] from {user[,user...]| Role|public} [CASCADE constrints]
Revoke system permissions with admin OPTION (permission reclamation does not cascade for system permissions and roles)
Revoke object permissions with Grant OPTION (permission reclamation has cascading applicable object permissions)
Same point:
-Two can either be used with user permissions or use the
Grant CREATE SESSION to EMI with ADMIN OPTION when assigning a role;
GRANT CREATE SESSION to role with ADMIN OPTION;
GRANT role1 to role2 with ADMIN OPTION;
Grant Select on Customers1-Bob with GRANT OPTION;
Grant Select on Customers1 to Hr_manager (role) with GRANT OPTION;
-Two empowered persons can assign permissions or role to other users
-two option can bring convenience to DBA and app ADMIN, but at the same time, it brings the factor of insecurity
Different points:
-with admin option can only be used when assigning to system privilege
-With GRANT option can only be used when assigning an object privilege
-When you revoke a system privileges with admin option, the associated permissions are preserved
For example:
1. The DBA gave the Create system permission to Jeff with ADMIN OPTION
2. JEFF creates TABLE
3. JEFF grants the CREATE TABLE System authority to EMI
4. EMI creates A table
5. DBA Revoke Create TABLE system permissions from Jeff
Results:
JEFF's table still exists, but cannot create a new table.
EMI's table still exists and he retains the Create TABLE system permissions.
-When you revoke an object privileges with GRANT option, the associated permissions are also undone
For example:
1. JEFF gave the Select object privileges on the EMP with ADMIN OPTION
2. JEFF gave the SELECT permission on the EMP to EMI
3. Later, revoke Jeff's SELECT permission
Results:
EMI permissions have been revoked.
Reprint http://hi.baidu.com/danghj/item/0737fa50f05217a8acc85798