The ABL security administrator is responsible for maintaining the ABL security information in the database. When a database is first created, everyone is a default security administrator. However, you should assign user IDs as the security administrator. If you plan to define user IDs in the database _User table accounts, you must also designate at least one user from these accounts as a security administrator. Note that once you add at least one individual user ID as a security administrator, no other user ID can function as a security administrator for a future connection to this database.
Caution: Make sure you can log into the database with a user ID before you assign it as a security administrator.
Typically, the database administrator also serves as security administrator. The security administrator uses:
The Data Dictionary, the Data Administration tool, or the Database Administration Console of OpenEdge Management or OpenEdge Explorer to establish connection, schema, and database access security at compile time or run time
An activity table provided by you (the developer) to establish run-time authorization for accessing specified precompiled procedures or classes
Note: SQL has its own administrator (DBA) to grant access privileges. The SQL DBA cannot set ABL permissions, just as an ABL security administrator cannot grant SQL privileges. For more information, see OpenEdge Data Management: SQL Development.
For more information about designating a security administrator or establishing and maintaining user IDs, passwords, and data access privileges, see OpenEdge Data Management: Database Administration and OpenEdge Getting Started: Identity Management.
The Data Dictionary, the Data Administration tool, or the Database Administration Console of OpenEdge Management or OpenEdge Explorer to establish connection, schema, and database access security at compile time or run time