Issue saving a Role

[didierfranc]

Hi, everything seems fine until I try to set ACL and Role.

[davidaik]

+1 We need fully working ACL and CLP.

[akships]

+1

[wangmengyan95]

Hi @didierfranc, is it possible for you to paste the stacktrace of your server?

[gfosco]

Roles and ACLs were implemented, and there are test scenarios you can see under the spec/ folder. If you can construct a failing test, that would be the most helpful, otherwise try to get the full response from the server and the logs.

[didierfranc]

Yes I saw that spec samples, I'll check that and post result here.

[didierfranc]

Maybe answer is that we can't use/set Roles as before

// Roles are not accessible without the master key, so they are not intended
// for use by clients.  We can manually test them using the master key.

https://github.com/ParsePlatform/parse-server/blob/master/spec/ParseRole.spec.js

[gfosco]

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.

[didierfranc]

@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 })

[gfosco]

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.

[ledowong]

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.
However for create/save, it only works with masterKey :(

It doesn't make sense to put the masterKey in JavaScript...
That mean whole thing broken now.

Any workaround? Thanks.

[ledowong]

@gfosco