Support different request type in one ABAC model

Hi All, I am using below ABAC config and I have defined the below two rules in the database:

[request_definition]
r = sub, obj, act

[policy_definition]
p = sub_rule, obj, act

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

[matchers]
m = eval(p.sub_rule) && r.obj == p.obj && r.act == p.act

Rules In Databas:

Id       PType      V0                                                                 V1        V2    V3      V4      V5
2070 p             r.sub.Age >=18 && r.sub.Age <=60             data1 read NULL NULL NULL
2071 p              r.sub.prodid==2018 && r.sub.version==58 data1 read NULL NULL NULL

var efCoreAdapter = new CasbinDbAdapter<int>(context);
var enforcer = new Enforcer("examples/abac_model.conf", efCoreAdapter);
enforcer.LoadPolicy();
Person p1 = new Person { Age = 19 };
enforcer.Enforce(p1, "data1", "read"); // This returns true as it maches the policyid 2070

// Similarly I defined another rule 2071 with attributes as prodid and versionid
        productdetails pdetails = new productdetails { prodid = 2018, version = 58 };
         enforcer.Enforce(pdetails, "data1", "read"); // This retuns below exception
System.ArgumentException: 'Object of type 'productdetails' cannot be converted to type 'Person'.'

Why it is taking Person as the default sub attribute and not taking the rule that is mentioned for productdetails? How to switch of casbin matches the subrule based on the roles policies defined in the table.?

[sagilio]

Because the same lambda will be cached for each different expression and the request type will be set depending on the first policy. In fact, Enforce will match the policies in order. Therefore, even without caching, A similar exception will be thrown for different request types.

DynamicExpresso.Exceptions.ParseException: 'No property or field 'Age' exists in type 'ProductDetails' (at index 6).'

You can write two model and policy files for Person and ProductDetails types to solve this question temporarily and we will try to provide a better API design on PR #94 to resolve this issue.

[sagilio]

closed by #230 , now we will use a different cache when request type is different