You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 18, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 18, 2020. It is now read-only.
I got the app up and running and then request the transactions from the test data user (1) using curl - so I am not passing a token, so I am not authenticated.
It happily returns all the transaction, which it shouldn't
Activity
74monkeys commentedon Dec 23, 2013
Some more info:
If I remove the following acl's then the access control works:
It's as if the property is not been read so it is interpreted as allowing all access.
{
"accessType": "",
"permission": "ALLOW",
"principalType": "ROLE",
"property": "findById",
"principalId": "$owner"
},
{
"accessType": "",
"permission": "ALLOW",
"principalType": "ROLE",
"property": "updateAttributes",
"principalId": "$owner"
},
{
"accessType": "*",
"permission": "ALLOW",
"principalType": "ROLE",
"property": "logout",
"principalId": "$everyone"
}
ritch commentedon Dec 23, 2013
@74monkeys Thanks for the report. I'm marking this as a bug and opening up a related bug in the loopback repo:
strongloop/loopback#115
crandmck commentedon Jul 8, 2015
As strongloop/loopback#115 has been closed, I'm going to close this as well.