Skip to content

Masterkey is not required and should not be available on client side #473

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
nstrelow opened this issue Oct 9, 2020 · 3 comments
Closed

Comments

@nstrelow
Copy link
Contributor

nstrelow commented Oct 9, 2020

I just learned today, that the Masterkey is only required for changing ACLs. I changed the key and my app was still working. Had a project for 6 months with Masterkey defined in the client app. Luckily not a production app.

Parse Server Readme: https://github.com/parse-community/parse-server#basic-options

The master key to use for overriding ACL security. You can use any arbitrary string. Keep it secret! For migrated apps, this should match your hosted Parse app.

Parse Client JS SDK Docs: https://docs.parseplatform.org/js/guide/

⚠️ If the Masterkey needs to be provided, use the following. Please note that the master key should only be used in safe environments and never on client side ‼️

Maybe we should add a similar strong disclaimer to our Readme?

@davidsowerby
Copy link

This was also raised in #417

@fischerscode
Copy link
Contributor

I think we can close this now, as #474 is part of the currently released version.

@nstrelow
Copy link
Contributor Author

great doc update :D

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

3 participants