Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

> ## Using the Security Control tool

> The Security Control tool allows you to define user types, security structures, and security allocations, which set the parameters of what administrators and users often call access rights.

> | To access the Security Control tool:

> 1. Select Tools Administration from the AppBuilder window.

> 2. Select Security Security Control from the Administration window.

> 3. To see all the Security control functions, expand the nodes of the tree, as shown in Figure 13–1.

> Figure 13–1: Security Control tool

> There are five major parts to the Security Control tool, as defined in the following table:

> Node | Purpose
> --- | ---
> Security control | The top node. All the global settings for security are found on this panel. See OpenEdge Development: Progress Dynamics Administration for more information.
> Security maintenance | Creates and modifies login companies, groups, users, and user categories as well as security structures for actions, data ranges, and fields. Security structures are security elements that identify existing application objects (for example, fields) to the security system or create application objects used by the security system (for example, data ranges).
> Security allocation | Associates users or groups with security structures to restrict or grant access to application functionality.
> Security enquiry | The security of an enterprise application can be extensive. The Security enquiry node is the best way for you to search for pertinent details before you make changes and to confirm the effect of your changes after they are made. With security enquiry, you can select a particular user and see how security allocations are resolved for that user. This is especially useful when the user belongs to multiple security groups or combined groups, or when the user is logged in under a particular login company.
> Security processing | Provides an option to convert a user security definition into a group definition. The process is as follows: Create a new group. Copy all security allocation of the user to the new group. Remove all security allocations from the user. Assign the user to the new group.

> When using the Security allocation nodes, you have several options for specifying who the security applies to and the login company context for those users. The effects of specifying login companies in allocations is described in Figure 13–2.

> Table 13–2: User names and login company security
> User or group name entered | Login company entered | Security applies to...
> Yes | No | The specific user or all members of the specified group (depending on your selections) regardless of what login company he or she logs in under (including no specific login company at all).
> No | Yes | All users who log in under that login company.
> Yes | Yes | The specific user or all members of the specified group (depending on your selections) when logged in under that company.

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