Permission Assignment on collection
I tried to assign permissions to a new group (in this case, Everyone) to an existing collection with over 50 sub-documents and other collections. Unfortunately, the permissions don't seem to trickle down to sub-documents and sub-collections. Now, I would normally have to select each sub-collection or sub-document and assign permissions to the group.
Is there an easier way to do this?
Is the database schema (Entity Relationship Diagram) for WSO2Registry published somewhere so that I could write a stored procedure to do this for me and feel confident that I didn't mess up the whole thing?
Thanks.
Bookmark/Search this post with:
- Login or register to post comments
- Printer friendly version
- 225 reads
Permission Assignment on collection
Hi,
Changes of permissions does not automatically apply to existing child resources and collections. But the child resources/collections added after changing the permissions will inherit the new permissions from the parent collection. We have implemented it this way because this is the most common use case. But it would be useful to recursively apply permissions in some situations as you have mentioned. We will consider adding this as an option for future releases.
I will publish the database schema of the registry soon. Till then you can find the SQLs for the database tables in https://wso2.org/repos/wso2/tags/registry/1_1/modules/core/src/main/resources/database-scripts/derby-complete.sql
Thanks,
Chathura