Policy effect allow-and-deny not return reason in EnforceEx
See original GitHub issueCurrent behavior
Using policy effect allow-and-deny some(where (p.eft == allow)) && !some(where (p.eft == deny))
, reason not include in result when has allow matched
Expected behavior
Return allow reason if there is at least one policy matched and no deny policy
If matched deny return deny reason
Other case return [] for reason mean not match allow and deny
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Returning a value of the policy rule as effect #46 - GitHub
Is it possible to define a model so I get that amount as a result of calling Enforce instead of a true/false effect?...
Read more >Casbin - Go Packages
AddGroupingPolicy adds a role inheritance rule to the current policy. If the rule already exists, the function returns false and the rule will...
Read more >Tanium™ Enforce User Guide
The policy is not in effect on the endpoint. This could be due to a timing issue if the policy has been sent...
Read more >Return products without order information - IBM
Sometimes, a customer may want to return a product and might not have order information associated with the product due to some reason...
Read more >PHP-Casbin - Giter VIP
In php-casbin, an access control model is abstracted into a CONF file based on the PERM metamodel (Policy, Effect, Request, Matchers).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
please review #363
🎉 This issue has been resolved in version 5.15.1 🎉
The release is available on:
Your semantic-release bot 📦🚀