Release 10.1A: OpenEdge Reporting:
Query/Results for UNIX

> ## Security options

> The Administration module has five security options:

> - Contents of a User Directory.

> - How to Exit Application.

> - Module Permissions.

> - Query Permissions.

> - Sign-on Program/Product Name.

> Use the Contents of a User Directory option to look at the contents of a user’s directory, the Module Permissions and Query Permissions to establish security for your application, and the How to Exit Application and Sign-on Program/Product Name options to change the Results exiting and startup interface. With the security options, you can establish permissions for each Results module and for each option in the Query module. You set permissions for specific files and fields using the OpenEdge Data Dictionary. (For more information, see the OpenEdge Data Management: Database Administration .)

> This section describes how to change the sign-on program and determines what appears when the user exits Results (operating system and so forth.). The "Sign-on program/product name" section describes how to modify your `login.p` file when you have security enabled for your database.

> You can set permissions on many different levels. For example, you can control the access one user or a group of users have to modules, menu options, query forms, and printers. You set permissions using `IDLISTs`.

> An `IDLIST` is an expression (a constant, variable, or any combination of these) whose value is a list of one or more user identifications (user IDs). If the expression contains multiple user IDs, you must separate the user IDs with commas. Do not insert blanks between the user IDs. Table 9–1 shows the values you can use in the `IDLIST`.

> Table 9–1: Values for IDLISTs
> Value | Meaning
> --- | ---
> * | All users are allowed access.
> `user` | This user has access.
> `!user` | This user does not have access.
> `string` | Users whose ID begin with string have access.
> `!string*` | Users whose ID begin with string do not have access.

> The `string` value is a character expression that the system checks against the `IDLIST`.

> For example, you can enter an `IDLIST` into the form shown in Figure 9–6 to establish permissions for the Administration module.

> Figure 9–6: Module permissions example

> In the `IDLIST` shown, the Administration module is available for users with a user ID that begins with mis, or for users with the ID of bill, kathy, tony, or irene.

> If you want to prevent access to the Update option in the Query module, you might enter the following `IDLIST` in the Query Permissions window as shown in Figure 9–7.

> Figure 9–7: Query option permissions example

> In the example, the `IDLIST` prevents all users whose user ID begins with acct from updating information in the Query module, unless the user ID is acctmngr. All other user IDs can use the Update option.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095