You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Deepak Dixit (Jira)" <ji...@apache.org> on 2026/05/22 06:53:00 UTC
[jira] [Assigned] (OFBIZ-13393) Review EntityPermissionChecker and remove framework dependency on Content/Party data model
[ https://issues.apache.org/jira/browse/OFBIZ-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepak Dixit reassigned OFBIZ-13393:
------------------------------------
Assignee: Deepak Dixit
> Review EntityPermissionChecker and remove framework dependency on Content/Party data model
> ------------------------------------------------------------------------------------------
>
> Key: OFBIZ-13393
> URL: https://issues.apache.org/jira/browse/OFBIZ-13393
> Project: OFBiz
> Issue Type: Sub-task
> Reporter: Deepak Dixit
> Assignee: Deepak Dixit
> Priority: Major
>
> The {{EntityPermissionChecker}} class currently appears to depend on the {{Content}} and {{Party}} data models for entity-level permission checks. Since {{Content}} and {{Party}} belong to the application layer, this creates an application dependency inside the framework.
> Classify each dependency as:
> * Required for framework security
> * Application-specific logic
> * Legacy/unused logic
> h4. Option A: Remove from framework
> If the class is unused or only supports application-specific Content/Party permissions:
> * Remove {{EntityPermissionChecker}} from framework.
> * Remove related configuration, imports, tests, and documentation.
> * Move the feature to the relevant application component if still required.
> h4. Option B: Decouple from Content/Party
> If the feature is still needed at framework level:
> * Replace direct entity lookups with a generic permission service.
> * Define a framework-level interface/service contract such as:
--
This message was sent by Atlassian Jira
(v8.20.10#820010)