![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#3
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#4
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#5
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#6
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#7
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#8
| |||
| |||
|
|
Is it possible to create a view based off DBA_ROLES so that a non-DBA user can keep track of which users belong to roles associated with his department? In this case, all roles associated with the specific department are named with a common prefix, e.g. ABC_<rest of role name>. I'm thinking of something like the following: CREATE VIEW ABC_USER_ROLES as SELECT USERNAME, GRANTED_ROLE FROM DBA_ROLES WHERE GRANTED_ROLE LIKE '%ABC_%'; Is there any technical or security issue in creating a view like this for the user. It would be a time-saver for all concerned to have the view (vs. generating static reports of what users are in which roles). |
#9
| |||
| |||
|
|
My reaction is that a stored procedure owned by some appropriately privileged schema that could be invoked by PUBLIC might be a better choice..- Hide quoted text - |
#10
| |||
| |||
|
|
My reaction is that a stored procedure owned by some appropriately privileged schema that could be invoked by PUBLIC might be a better choice..- Hide quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |