You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

DualShield employs the Role Based Access Control (RBAC) model for access control to the Management Console. 

  •  A user belongs to or has one or many roles
  •  A role has a set of access permissions
  •  A permission is right to execution or access

An administrative role is a collection of permissions that can be assigned to an administrator. A role determines what level of control the administrator has over which objects, such as users, tokens, reporting etc.

You can add as many custom administrative roles as your organization needs. You can also assign multiple roles to a single administrator. When an administrator has more than one role, the privileges granted by those roles are combined, allowing the administrator to perform any action granted by the assigned roles.

For example, suppose an administrator is assigned one role that grants permission to view and edit users, and another role that grants permissions to view and edit user groups. Each time the administrator logs on, he or she can view and edit both users and user groups.

A role has 3 properties:

  • A descriptive name
  •  A set of managing domains
  • A collection of permissions based on the function of the role 

A permission has 3 components:

  •  A set of scopes
  • A set of objects
  • A set of actions

The managing domains of an administrative role determine the domains in which the role lives and is managed (by other administrative users with the right to manage roles).

The scope of an administrative role determines in what scope administrator may manage objects.

Actions assigned to the administrative role determine what actions an administrator assigned the role can take on objects such as users, user groups, security domain, units, and various policies. The following common privileges are available for all objects:

  1. All grants an administrator permission to perform any administrative action on the object.
  2. Create grants an administrator permission to create/add an object.
  3. Delete grants an administrator permission to delete an object.
  4. Edit grants an administrator permission to view and edit an object, but not the ability to create or delete.
  5. View grants an administrator permission to view an object, but not the ability to add, edit, or delete.      

Each object may also have its own special privileges.

You can only assign and add administrative roles with the same or fewer objects than the administrative role assigned to you.

You can only assign and add administrative roles with the same or fewer privileges than the administrative role assigned to you.

How to Create a Help Desk Role in DualShield

Help desk operator is an administrator, typically with restricted access to the management console.  For instance, below is a list of permissions that are typically assigned to help desk operators:

  1. Issue Emergency Code
  2. Reset Passwords
  3. Lock/Unlock. Enable/Disable user accounts
  4. Craete and View reports

 To create a role, select "Administration | Roles" in the main menu, click "Create" button on the toolbar:

    

The "Domain" field is the so-called Managing Domain. If a role has managing domains, then the role can only be managed by administrative users in the managing domains who have the right to manage roles. If a role does not have managing domains, then the role can be managed by all administrative users who have the right to manage roles.

Once a role is created, you can add and edit its persimmisons. Click the context menu icon of the role, select "Permits":

    

To create a new permit for the role, click "Create" on the toolbar:

    

Select "Scope", "Object" and "Actions" and press "Save" to save it.

Repeat the same process to create all other permits for the role:

      

Finally, do not forget to assign the role to a user or user group.