Closed iamhosseindhv closed 3 years ago
I believe this is a bug. When calling removeFilteredNamedPolicy, sec or ptype values aren't respected.
removeFilteredNamedPolicy
sec
ptype
Example
table content id, ptype, v0, v1, v2, ... 1, p, user:1, table, read 2, p, user:1, desk, read 3, g, user:1, role:admin 4, p, user:2, desk, delete
enforcer.removeFilteredNamedPolicy('p', 0, 'user:1')
To remove rows 1,2. i.e. policies that are applied to a user
Removes rows 1,2 and 3. i.e. also removes grouping policies for user:1
user:1
@Zxilly @Gabriel-403
working on this
:tada: This issue has been resolved in version 2.3.1 :tada:
The release is available on:
npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:
I believe this is a bug. When calling
removeFilteredNamedPolicy
,sec
orptype
values aren't respected.Example
Expected Behaviour
To remove rows 1,2. i.e. policies that are applied to a user
Actual Behaviour
Removes rows 1,2 and 3. i.e. also removes grouping policies for
user:1