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 : Creating an application activity permissions table
 
Creating an application activity permissions table
You create a permissions table within the Data Dictionary. This chapter calls the table permissions, but you can use any name you want. Each record in the permissions table contains at least two fields: an activity field and a can–run field. The activity field contains the name of the procedure and the can–run field contains a comma-separated list of the user IDs of those users who have permission to run the procedure. (Whether these are database connection or OpenEdge session IDs depends entirely on how you match them with the CAN-DO function.) Normally, the primary index is built on the activity field.
After you create a permissions table, you must add a record for every application activity for which you want to provide security.