Kbase P125990: What does selecting the "Use Runtime Permissions Checking" database option mean?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/29/2008 |
|
Status: Verified
GOAL:
What does selecting the "Use Runtime Permissions Checking" database option mean?
GOAL:
How to specify the run-time permissions data security checking?
GOAL:
Does specifying the "Use Runtime Permissions Checking" database option allow a user to compile code against tables for which he has no data access permissions?
GOAL:
Does selecting the "Use Runtime Permissions Checking" database option replace the default compile time data security checking with runtime data security checking?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
FIX:
1. To specify the run-time permissions data security checking:
1.1. Access the Data Administration tool if you are using a graphical interface or the Data Dictionary if you are using a character interface.
1.2. Choose Admin > Database Options to access the Database Options dialog box appears.
1.3. Check the "Use Runtime Permissions Checking" database option mean and click OK.
2. The Database data security checking is always enforced at compile time. Selecting "Use Runtime Permissions Checking" database option causes the user table and field security permissions to be checked at both compile time as well as run time. Hence, if the "Use Runtime Permissions Checking" is NOT set, only authorized users can compile source code and the generated r-code may be run by any other user. On the other hand, if the "Use Runtime Permissions Checking" IS set, then only authorized users can compile source code and the generated r-code may be run ONLY by authorized users.
3. Specifying the "Use Runtime Permissions Checking" database option does not replace the compile time data security checking but augments it with runtime data security checking . In other words, the user permissions are checked in both compile and runtime.