...
After creating a new RXT file via a new user role, you need to set permissions using the following methods to provide READ, WRITE, DELETE, and AUTHORIZE permissions to the parent collection path.
| Tip |
|---|
Permissions are set by default for the default user roles and artifact types. You need to set permission for the roles created by you for the new artifact type that you are creating. |
Using the management console
...
- Log in to the WSO2 G-Reg Management Console, and click Main → Resources → Browse.
- Navigate to the parent collection (e.g.,
/_system/governance/test/contacts/names) and click on it. - Add the new role in the Permissions section as shown in the example below. For more information, see Role Permissions.
Using the product binary distribution
...
- Open the
<G-REG_Home>/repository/conf/etc/permission-mappings.xmlfile. Add following configuration configurations to the end of the file.
Code Block language xml <mapping managementPermission="/permission/admin/manage/resources/govern/imapersonne/add" resourcePermission="http://www.wso2.org/projects/registry/actions/get" resourcePaths="/_system/governance/ima/contacts/personnes"/> <mapping managementPermission="/permission/admin/manage/resources/govern/imapersonne/add" resourcePermission="http://www.wso2.org/projects/registry/actions/add" resourcePaths="/_system/governance/ima/contacts/personnes"/> <mapping managementPermission="/permission/admin/manage/resources/govern/imapersonne/add" resourcePermission="http://www.wso2.org/projects/registry/actions/delete" resourcePaths="/_system/governance/ima/contacts/personnes"/> <mapping managementPermission="/permission/admin/manage/resources/govern/imapersonne/list" resourcePermission="http://www.wso2.org/projects/registry/actions/get" resourcePaths="/_system/governance/ima/contacts/personnes"/>
...