Skip to content

Live queries not fired for objects with Role ACL protection when _Role objects are not publicly open #4311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
frangulyan opened this issue Nov 1, 2017 · 2 comments

Comments

@frangulyan
Copy link

frangulyan commented Nov 1, 2017

I have Role class with read-only CLP and objects in it with Master Key Only ACL.
I have class A (read/write CLP) on which I want to do live queries, it's objects are protected by ACLs giving a read-only access to a particular role. Then I subscribe for live query from iOS SDK with a user which has the correct role for the given object. When I change objects the live query events are not fired back to iOS. Whenever I change the ACL of the corresponding role from Master Key Only to Public Read the iOS starts receiving live query events.

I would expect that live query server will have master key access to Role table, I wonder if this is by design and I have to open Role table for live queries to work.

I am using back4app service for hosting parse server, will not be able to fill out all the data below

  • Server

    • parse-server version: 2.3.3
    • Operating System: N/A
    • Hardware: N/A
    • Localhost or remote server?: AWS, if not mistaken
  • Database

    • MongoDB version: N/A
    • Storage engine: N/A
    • Hardware: N/A
    • Localhost or remote server?: AWS, if not mistaken
@frangulyan frangulyan changed the title Live queries not fired for objects with Role ACL protection Live queries not fired for objects with Role ACL protection when _Role objects are not publicly open Nov 1, 2017
@frangulyan
Copy link
Author

frangulyan commented Nov 1, 2017

Related discussions were found here - 106, 2018, 349, 40

@stale
Copy link

stale bot commented Sep 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Sep 18, 2018
@stale stale bot closed this as completed Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant