Open topic with navigation

Overview of User Security

User access to applications, functionality and even projects in OEDQ employs a users and groups model.

In OEDQ, a central security policy defines the general password settings, such as the password security requirements, password expiry and the required behavior following unsuccessful attempts to log in. For more details on setting a central security configuration, see Changing the security configuration.

Some aspects of the security configuration can be overridden on a per-user basis, in particular, password expiry and the behavior after a number of failed login attempts. For more details on creating and editing users and their individual security configuration, see Creating and Editing Users.

Users and Groups

The users and groups model centralizes the allocation of functional permissions and application access right. This reduces the amount of repeat configuration required for each user, and helps to standardize the granting of permissions across the whole company. In brief:

• User groups are created to represent each of the various roles that a user may fulfil in OEDQ;
• Functional permissions, such as 'Add Process', are granted to the appropriate user groups;
• Application access permissions are granted to the appropriate user groups;
• Optionally, project access can be restricted to selected groups;
• Users are created and assigned to the user groups required to carry out their work in OEDQ.

The following diagram illustrates the relationship between internal users, user groups and the different kinds of access permissions, showing the central nature of the user groups:

Users and Groups in External User Management

If you have integrated OEDQ with Active Directory, the users and groups model is slightly different. Instead of creating users within OEDQ and mapping them directly to the OEDQ user groups, users are created in the LDAP directory and assigned to LDAP groups. The LDAP groups are then mapped to the OEDQ user groups, which are assigned application, functional and project permissions as described above:

For more information on this, please refer to the Integrating OEDQ with Active Directory topic.