-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Issue saving a Role #80
Comments
+1 We need fully working ACL and CLP. |
+1 |
Hi @didierfranc, is it possible for you to paste the stacktrace of your server? |
Roles and ACLs were implemented, and there are test scenarios you can see under the |
Yes I saw that |
Maybe answer is that we can't use/set Roles as before
https://github.com/ParsePlatform/parse-server/blob/master/spec/ParseRole.spec.js |
Well, roles even on hosted parse require the master key. So this is working as intended. Initialize with the master key and pass useMasterKey: true in the save call. |
@gfosco The function in the first post is part of my installation script to define an admin, user roles ... it runs (client side) well with Parse.com not with the new parse-server. So everything is fine if I set the masterkey Parse.masterKey = 'myMasterKey'
// ...
role.save({}, { useMasterKey: true }) |
I check and you're right, the REST API Key was allowed to affect Roles on hosted Parse... I think it's better here in parse-server to require the master key. |
I used very long time to find this post. I think this should be in the README because it is very very important. For me, my app is a web app using JS SDK. Now read Role, create object and save object are not working....... For read Role, I can just hardcode my username, to check if the loggedIn user is allowed to edit. It doesn't make sense to put the masterKey in JavaScript... Any workaround? Thanks. |
I opened this thread, I gave the non solution of masterkey I'll work on a real one based on Cloud code |
+1 |
Hi, everything seems fine until I try to set ACL and Role.
The text was updated successfully, but these errors were encountered: