Try OpenEdge Now
skip to main content
Programming Interfaces
Data Management : Application Security : Authorizing access to procedures and database resources : Defining activities-based user authorization
 
Defining activities-based user authorization
Applications that you write probably break down into several areas or activities. For example, you may have one set of procedures that handles Customer activities, and another set that handles inventory activities. For each set of activities, you may want to establish a valid group of users. To do this, you build a permissions table. To establish and use a permissions table, you must:
*Create a table that defines the kinds of access different users have to application activities.
*Include statements in application procedures to check the permissions table at run time.
*Write a procedure that can modify access permissions.
* Creating an application activity permissions table
* Adding records to the permissions table
* Including security checking in procedures
* Protecting and maintaining the permissions table