Page Comparison

The "Permissions" panel  panel shows the defined role permissions, and allows to add new role permissions and edit existing ones.

Image RemovedImage Added

Adding New Role Permissions

...

...

1. In the "New Role Permission" panel, select a role to set a permission.

Image Modified

Info
title Note
The "wso2.anonymous.role" is a special role that represents a user that has not logged into the WSO2 Governance Registry Management Console. Granting "Read" access to resources for this role would mean that you do not require authentication to access resources using the respective Permalinks. The "everyone" role is a special role that represents a user that has logged into the WSO2 Governance Registry Management Console. Granting "Read" access to a resource would mean that any user who has logged into the Management Console with sufficient permissions to access the Resource Browser can read the respective resource. Granting "Write" or "Delete" access to a resource would mean that any user who has logged into the Management Console with sufficient permissions to access the Resource Browser  can make changes to the respective resource.

...

• Read
• Write
• Delete
• Authorize

Info
title Note
"Authorize" is a special permission that gives a role the ability to grant and revoke permissions.

Image Modified

3. Select whether to allow or deny the action for the selected role or deny.

Info
title Note
"Deny" Denied permissions have higher priority over "Allow" allowed permissions. Essentially, this means that a "Deny" denied permission always overrides an "Allow" allowed permission assigned to a role. "Deny" permission Denied permissions must be given set at the collection level. For example, If the user does if you want to "Deny" deny the write/delete action on a given policy file, User you should set the permission to "for Write/Delete " to "Deny" for the his role at the "/trunk/policies" level. If the user gives the "Deny" permission you set the permission to Deny beyond the collection level (eg e.g.: / or /_system...etcsystem…etc), it will not be applied for to the user 's role.

...

4. Click on the "Add Permission" button.Image Removed

5. A The new permission appears in the "Defined Role Permissions" list.

Image Removed

Editing Role Permissions

...

...

1. Existing permissions can be changed by selecting and clearing the check boxes for the required permissions in the "Defined Role Permissions" list list.

Image RemovedImage Added

2. After editing the permissions, click on the "Apply All Permissions" button to save the alterations.Image Removed

Excerpt
hidden true
Instructions on how to manage Resources role permissions in WSO2 Governance Registry.