Compile-time authorization (the default), which requires ABL procedures and classes to have authorization to compile against a particular database. For information on compile-time authorization, see OpenEdge Deployment: Managing ABL Applications.
Run-time authorization (optional), which includes setting an option to check OpenEdge RDBMS table and field permissions in ABL procedures and classes at run time, using the DBAUTHKEY configuration option of the PROUTIL utility to require run-time permissions checking of ABL procedures and classes that have previously passed compile-time permissions checking, and using the Type of Server to Start (-ServerType) startup parameter to restrict the type of server (SQL or ABL) that accesses the OpenEdge RDBMS. For information on run-time authorization for ABL procedures and classes, see OpenEdge Deployment: Managing ABL Applications, on the DBAUTHKEY option, see OpenEdge Data Management: Database Administration, and on the Type of Server to Start (-ServerType) startup parameter, see OpenEdge Deployment: Startup Command and Parameter Reference.
Cryptography, which ensures that unauthorized users cannot read or change data. For more information on cryptography and the cryptographic features of ABL, see Cryptography.
Caution: Progress Software Corporation recommends that you use the cryptographic features of ABL only if you have a well-grounded understanding of cryptography and its usage. Use of cryptography without the necessary preparation can result in permanent data loss. In general, cryptography can have significant negative impact on application performance and decrease effective data compression for data stored in a database.
Transparent Data Encryption (TDE) to provide data privacy while the data is "at rest" in an OpenEdge database. For more information, see Transparent Data Encryption in OpenEdge RDBMS.
Database connection authorization using SSL (see Database security.