fix(policy): DPSX-4630 PDP allows permits decisions on inactive attribute values with direct entitlements - #3984
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe PDP test suite adds active and inactive values to a third attribute. New subruns verify denial for inactive values and mixed active/inactive resources, plus access for an active value when its sibling is inactive. ChangesDirect entitlement decision tests
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change adds regression coverage for direct entitlements involving inactive attribute values without altering production behavior. The new cases cover inactive-value denial, mixed-value denial, and continued access for active siblings, with no current merge-blocking risk identified. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Benchmark results, click to expandBenchmark authorization.GetDecisions Results:
Benchmark authorization.v2.GetMultiResourceDecision Results:
Benchmark Statistics
Bulk Benchmark Results
TDF3 Benchmark Results:
|
Proposed Changes
Bug
Existing logic in the access PDP is allowing direct entitlements passed in from an entity representation to bypass active/inactive checks on attribute values when making a permit/deny decision. A simple test has been added to verify the initial bug.
Checklist
Testing Instructions