The Featured Content microservice powering the Unified UI appears to be improperly evaluating identity mapping. Because our namespaces are defined but user enforcement is turned off, the API fails to route unscoped global curated rules to the frontend, resulting in a 403.
Architecture: Multi-tenant environment using namespaces (Customer A, Customer B) for logical isolation.
Current State: Data Access Paradigm Enforcement is currently Disabled/Inactive as our unified analyst team manages all clients globally.
Troubleshooting Already Performed:
Verified the user has the required legacy permissions (chronicle.curatedRules.*, chronicle.curatedRuleSets.*). The standalone "Curated Detections" tab loads and functions perfectly.
Verified the user has the required new permission (chronicle.featuredContentRules.list) attached to their custom Alpha role.
