When a WinGate component has a feature or user interface that can be controlled by permissions, it will register each of them with the Permissions system as a permission object. You can then use the properties of each permission object to set permissions that will apply to that particular part of the component. This allows you to configure what access and control users and groups have to the various features and dialogs of each component.
Registered permission objects can be accessed and configured from two places in WinGate:
When a user interface dialog is registered as a permission object, the dialog will have a permissions tab so you can configure permissions for the relevant feature.
Located at Control Panel > Permissions in the WinGate Management console, the Permissions panel will display all of the permission objects that WinGate components have registered with the Permissions system. The panel displays the permissions tree which is used by the Permissions system to group permission objects into a branch according to the component that registered them.
In the permissions tree of the Permissions panel, components will register a container permission object that will hold all the other permission objects registered by that component. These container permission objects allow you to set broader access and control to the component itself by users and groups. As such, container permission objects (referred to as parents in the permissions tree) allow you to set permissions that will be applied to all child permission objects inside the container. This parent - child relationship allows you to set tighter permissions for users and groups on individual child permission objects. This is useful when you want to allow users access or control to certain features and configurations of a module, but not to others.
Often modules allow you to create new items when configuring them in the WinGate Management console. These can include such things as new certificates, policies, profiles etc. Whenever you create a new item that can have permissions set on it, the item will be registered as a permissions object.
For example, whenever someone creates a policy in the Policy system, the new policy is registered as a permissions object. Using the Permissions panel, or Permissions tab of the relevant policy, you can set access and control permissions to the new policy configuration on a user or group basis.
Although permissions can be set on a granular, per child permission object basis, the users and groups affected by these permissions require at least a Read permission for the component parent container in order to see and access the appropriate feature, dialog etc. in the WinGate Management console.
©2012 Qbik New Zealand Limited
no comments yet...
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
You can create a new account or reset your password at forum.wingate.com.