As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
How do I offer access of a private collection to another user?
j
jamesw6811
started a topic
about 9 years ago
I have a collection of entries, which should be private per user. When a sharing request is accepted, I would like to make all entries in this collection from one user visible to another specified user.
The only way I know of doing this right now is setting every entity's properties separately (which seems like it could mean a performance hit) or by customizing the fetch endpoint (which seems like it has security risks associated -- i.e. users can still get data using COUNT requests). I've already implemented the latter.
Note: I would like to make this change on the server-side (i.e. from a hook or endpoint), so that our clients don't have to implement this functionality.
Hey James, I think you are on the right track. If you use ACL's instead of restricting through BL, then _count would respect that. The best way to do that is via the REST API. I put up a post about usergroups and permissions here, which may help: https://support.kinvey.com/discussion/comment/201904552
Gal
said
about 9 years ago
Hi James,
It does sound like groups provide the functionality you are looking for. Currently, while adding groups to entity ACLs is supported through the client libraries, group creation and modification is only provided through the REST API.
j
jamesw6811
said
about 9 years ago
Do you have an example of using the REST API in Business Logic? I need to create a group whenever a user is created and add someone to a group during a custom endpoint.
jamesw6811
The only way I know of doing this right now is setting every entity's properties separately (which seems like it could mean a performance hit) or by customizing the fetch endpoint (which seems like it has security risks associated -- i.e. users can still get data using COUNT requests). I've already implemented the latter.
Note: I would like to make this change on the server-side (i.e. from a hook or endpoint), so that our clients don't have to implement this functionality.