We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
User collection级别的ACL如下:
create: 'role:admin', delete: 'role:admin', find: 'role:admin', get: 'public', update: 'public'
某row的ACL如下:
{ objectId: '123456', username: 'tester', ACL: { "*": {read: true}, "123456" {write: true}, "role:admin": {write: true} } }
已经创建并关联了admin role
admin
tester
以上三条是预期的结果, 但是下面这条就不知为何了.
另外, 还想知道ACL规则的权重是如何计算/合并的?
The text was updated successfully, but these errors were encountered:
👍
Sorry, something went wrong.
补充, 同样的ACL rule在其他业务model上是按照预期工作的
User 表与其他表不同,有一条额外的规则只允许某个 user 对应的 session update。这条规则的优先级比 Class 权限要高。(@sunchanglong 或许在控制台禁用掉 User 表 update: public 这一选项?)
当然 User 表依然可以通过 masterKey 来修改。
No branches or pull requests
User collection级别的ACL如下:
某row的ACL如下:
已经创建并关联了admin role
通过RESTful API访问/更新用户资料时有以下问题:
admin
可以findtester
不可以findtester
可以通过自己的sessionKey修改自己以上三条是预期的结果, 但是下面这条就不知为何了.
admin
无法通过自己的sessionKey修改tester
另外, 还想知道ACL规则的权重是如何计算/合并的?
The text was updated successfully, but these errors were encountered: