Skip to content
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

ACL compatibility problem between parse.com and parse-server #1150

Closed
carmenlau opened this issue Mar 23, 2016 · 5 comments
Closed

ACL compatibility problem between parse.com and parse-server #1150

carmenlau opened this issue Mar 23, 2016 · 5 comments
Labels
type:question Support or code-level question

Comments

@carmenlau
Copy link
Contributor

During migration, it is difficult to avoid using parse.com server and self hosted parse-server at the same time. As per mentioned on issue #167, _acl has migrated to new structure _wperm and _rperm. The data will be inconsistent if we run parse.com cloud code and parse-server at the same time. For example, if we update ACL in the new app, but ACL in the old app will remain unchanged. Or create a new object in new app, the ACL object will be empty in the existing parse.com cloud code.

@carmenlau carmenlau changed the title ACL compatibility problem ACL compatibility problem between parse.com and parse-server Mar 31, 2016
@carmenlau
Copy link
Contributor Author

After doing more test I found following behavior.

parse.com
Update: _acl, _wperm and _rperm
Read: _acl

parse-server
Update: _wperm and _rperm
Read: _wperm and _rperm

Not sure is it a good suggestion if we change parse-server to update acl both way (include _acl) to solve the compatibility problem? Or parse.com will change to read _wperm and _rperm in future?

@gfosco Regarding to your comment in #167, I think you can give some comments on this too. Any comments would be appreciated!

Thanks a lot!

@dvanwinkle
Copy link

I'm not sure if this should be added to this or made a separate issue, so, I apologize if this is the wrong place for this. It could be related, so, I'm defaulting to adding it to the Issue.

If you have Public Read/Write CLP's enabled and you use Pointer permissions, Parse.com server will still return the same as Public Read/Write, but, Parse Server will return only records that apply to the Pointer Permissions. This is most likely an edge case, but, I can see people wanting Public Read and only allow Write based off of an Pointer CLP. If this is unclear, I can try my best to help.

@flovilmart
Copy link
Contributor

It seems to be a bug in the pointer permissions. I'll have a look later

@flovilmart
Copy link
Contributor

Related to #1953

@flovilmart
Copy link
Contributor

@carmenlau looking at the PR, I believe the original issue has been fixed. Feel free to reopen if it isn't the case

@mtrezza mtrezza added type:question Support or code-level question and removed 🔧 troubleshooting labels Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:question Support or code-level question
Projects
None yet
Development

No branches or pull requests

4 participants