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
There is an old design flaw in privilege schema, that multiple privileges may match the same path. It is described in README:
However of all the matching rules only the rule with the longest path pattern will be used to determine whether a user is allowed to perform a request. This is often a bit surprising.
This is implemented as:
ORDER BY length(path) - length(replace(path, '/', '')) DESC
To make it less "surprising" we can use ordered rules (the first to match wins).
Instead of order, this might be, reversed, weight. With the default value length(path) - length(replace(path, '/', '')) in SQLite, and something like that on Postgres side.
Activity
ip1981 commentedon Jul 22, 2017
Instead of
order, this might be, reversed,weight. With the default valuelength(path) - length(replace(path, '/', ''))in SQLite, and something like that on Postgres side.