You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/03/09 16:44:40 UTC
[jira] [Updated] (JCR-3830) Allow for privilege discovery in
jcr-server
[ https://issues.apache.org/jira/browse/JCR-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-3830:
--------------------------------
Description:
in order to allow for implementing {{AccessControlManager.hasPrivilege}} and {{AccessControlManager.getSupportedPrivileges}}, the dav resources in jcr-server should allow to retrieve the following protected properties:
- SUPPORTED_PRIVILEGE_SET : on the workspace resource and on node-resources
- CURRENT_USER_PRIVILEGE_SET : on the workspace resource and on node-resources
since {{Session#isGranted}} is already covered by the {{JcrPrivilegeReport}} (which would better be called JcrActionsReport), it should be save to replace the current implementation of CURRENT_USER_PRIVILEGE_SET on {{AbstractItemResource}} which in this current from doesn't make too much sense in jcr-remoting situation based on JCR 283.
was:
in order to allow for implementing {{AccessControlManager.hasPrivilege}} and AccessControlManager.getSupportedPrivileges}}, the dav resources in jcr-server should allow to retrieve the following protected properties:
- SUPPORTED_PRIVILEGE_SET : on the workspace resource and on node-resources
- CURRENT_USER_PRIVILEGE_SET : on the workspace resource and on node-resources
since {{Session#isGranted}} is already covered by the {{JcrPrivilegeReport}} (which would better be called JcrActionsReport), it should be save to replace the current implementation of CURRENT_USER_PRIVILEGE_SET on {{AbstractItemResource}} which in this current from doesn't make too much sense in jcr-remoting situation based on JCR 283.
> Allow for privilege discovery in jcr-server
> -------------------------------------------
>
> Key: JCR-3830
> URL: https://issues.apache.org/jira/browse/JCR-3830
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr-server
> Reporter: angela
> Assignee: angela
> Priority: Minor
> Fix For: 2.9.1
>
>
> in order to allow for implementing {{AccessControlManager.hasPrivilege}} and {{AccessControlManager.getSupportedPrivileges}}, the dav resources in jcr-server should allow to retrieve the following protected properties:
> - SUPPORTED_PRIVILEGE_SET : on the workspace resource and on node-resources
> - CURRENT_USER_PRIVILEGE_SET : on the workspace resource and on node-resources
> since {{Session#isGranted}} is already covered by the {{JcrPrivilegeReport}} (which would better be called JcrActionsReport), it should be save to replace the current implementation of CURRENT_USER_PRIVILEGE_SET on {{AbstractItemResource}} which in this current from doesn't make too much sense in jcr-remoting situation based on JCR 283.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)