Configuring role-based security from Dynamic Workload Console

This section explains how to create and modify the security objects by using the Manage Workload Security interface from Dynamic Workload Console.

To create or modify security objects, you must have permission for the modify action on the object type file with attribute name=security.

When working with the role-based security from Dynamic Workload Console, be aware that access to security objects is controlled by an "optimistic locking" policy. When a security object is accessed by user "A", it is not actually locked. The security object is locked only when the object update is saved by user "A", and then it is unlocked immediately afterwards. If in the meantime, the object is accessed also by user "B", he receives a warning message saying that the object has just been updated by user "A", and asking him if he wants to override the changes made by user "A", or refresh the object and make his changes to the updated object.