Each operating system provides security measures that you can use to protect r-code, procedure libraries, and database files for access by other OS user accounts and OS administrators.
On UNIX, you can use operating system file security to protect your procedure files in addition to, or instead of, including security checking in the application procedures. If you, as the application administrator, want to be the only user allowed Write access to p-adcust.p when everyone else has only Read access, you should create the source and r-code files with your user ID, then change the permissions for the files accordingly. To change the permissions for p-adcust.p, enter one of the following UNIX commands:
chmod 640 p-adcust.p
chmod 640 p-adcust.r
These permissions indicate that you are the only user allowed to read from (R) and write to (W) p-adcust.p. No other users are allowed any kind of access to that procedure.
In Windows, you can set authorization on a specific file or directory through the file or directory's properties. For example, if you want to set permissions for p-adcust.p, in Windows Explorer right-click on the file and select Properties from the pop-up menu. The Properties dialog box appears:
After you click the Security tab, you can specify various levels of authorization to the file. You can also click the Advanced button to set additional security options.
For more information about using the operating system to protect database files, see OpenEdge Data Management: Database Administration. For more information about setting operating system permissions, see your operating system documentation.
