Support for different definitions?

[judahb]

Can i modify the definition in the express example to support a modified RBAC with domains/tenants? Meaning is a custom definition supported?

[tiagostutz]

Maybe you could implement is as another example...
You could rename the current example folder to "examples" and create 2 folders there: one that will have the current example (the folder could be named "simple") and another with this example you are proposing...

What do you think?

[judahb]

I need to build this for a solution that will be open sourced. So while i can do that as an example, I would prefer to know if a different definition is supported so i can get to work. If not, i will likely need to approach this differently.

[judahb]

Seems like that response was duplicated?

[tiagostutz]

I would prefer to know if a different definition is supported so i can get to work

What do you exaclty mean by "different definition is supported"? You are supposed to be able to use all the definitions supported by Casbin. If you know Casbin supports the definition you are looking for, then it should work here also. If it doesn't we can fix it to do so.

[judahb]

Acknowledged. Thanks alot for the update. I will test the definition provided by casbin, and will let you know if i have any challenges.

[tiagostutz]

Nice! I'm waiting for your updates.
Cheers!

PS - My Internet was a mess here, so my last messages were duplicated and misformatted... fixed them now.....ehehehheehhe.

[judahb]

This will not work with definition below. Reason is the code is hardcoded to if(enforcer.enforce(username, path, method)) {

[request_definition]
r = sub, dom, obj, act

[policy_definition]
p = sub, dom, obj, act

[role_definition]
g = _, _, _

[policy_effect]
e = some(where (p.eft == allow))

[matchers]
m = g(r.sub, p.sub, r.dom) && r.dom == p.dom && r.obj == p.obj && r.act == p.act

[judahb]

Also, it seems it ignore 'g', is that correct? I need roles for my multi tenant approach

req.originalUrl.match(new RegExp(ignoredPathsRegex, "g"))

[tiagostutz]

"g" is for "Global match" in the regex... so it would look for all the occurrences of the ignoredPathsRegex within the URL.

[tiagostutz]

@judahb can you provide an example showing "values" of your request? I mean, showing URLs and roles involved in a request and how would they should be handled?

[hsluoyz]

@tiagostutz I think @judahb means that the enforcement code is written as:

if(enforcer.enforce(username, path, method)) {

But the request part in the model is:

[request_definition]
r = sub, dom, obj, act

The dom arg needs to be passed into the enforce() function:

const domain = "domain1";
if(enforcer.enforce(username, domain, path, method)) {

Is there any way to support the domain arg easily in this repo?