You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2011/02/09 18:59:58 UTC
[jira] Created: (JCR-2887) Split PrivilegeRegistry in a per-session
manager instance and a repository level registry
Split PrivilegeRegistry in a per-session manager instance and a repository level registry
-----------------------------------------------------------------------------------------
Key: JCR-2887
URL: https://issues.apache.org/jira/browse/JCR-2887
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-core, security
Reporter: angela
Assignee: angela
in order to resolve the privilegeregistry related TODOs within jackrabbit-core, i would like to split off those
methods from PrivilegeRegistry that are used on a per-session level (including jcr-names) and add them
to a manager class that was present with each session context. consequently the responsibility of the
registry was then limited to read/build the privilege definitions and would be present on the repositorycontext
deprecating those methods that would be covered by the manager).
in addition the naming was then consistent with what we use to have for nodetypes and namespaces.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Updated] (JCR-2887) Split PrivilegeRegistry in a
per-session manager instance and a repository level registry
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
Yes, see the recent "more frequent releases" thread and the 2.3.0 release
plan.
The idea is basically that we'll cut more frequent "unstable" releases
directly from trunk, and then make a stable 2.4 release branch later.
BR,
Jukka Zitting
On Sep 28, 2011 10:16 AM, "Angela Schreiber" <an...@adobe.com> wrote:
> hi jukka
>
> then i'm having a basic lack of understanding regarding 2.3.0.
> i thought 2.3.0 will be the next version of jackrabbit
> being released next year with the next version of cq?
>
> did that plan change?
>
> regards
> angela
>
> On 9/28/11 8:57 AM, Jukka Zitting wrote:
>> Hi Angela,
>>
>> On Wed, Sep 28, 2011 at 8:40 AM, angela (Updated) (JIRA)
>> <ji...@apache.org> wrote:
>>> angela updated JCR-2887:
>>> ------------------------
>>>
>>> Fix Version/s: 2.3.0
>>
>> I dropped the Fix Version from the issue since it wasn't yet fully
>> resolved in the 2.3.0 release candidate I cut yesterday. I'd recommend
>> either leaving the Fix Version unset or setting it to 2.3.1 or 2.4
>> depending on the estimated time-scale of a resolution.
>>
>> BR,
>>
>> Jukka Zitting
Re: [jira] [Updated] (JCR-2887) Split PrivilegeRegistry in a per-session
manager instance and a repository level registry
Posted by Angela Schreiber <an...@adobe.com>.
hi jukka
then i'm having a basic lack of understanding regarding 2.3.0.
i thought 2.3.0 will be the next version of jackrabbit
being released next year with the next version of cq?
did that plan change?
regards
angela
On 9/28/11 8:57 AM, Jukka Zitting wrote:
> Hi Angela,
>
> On Wed, Sep 28, 2011 at 8:40 AM, angela (Updated) (JIRA)
> <ji...@apache.org> wrote:
>> angela updated JCR-2887:
>> ------------------------
>>
>> Fix Version/s: 2.3.0
>
> I dropped the Fix Version from the issue since it wasn't yet fully
> resolved in the 2.3.0 release candidate I cut yesterday. I'd recommend
> either leaving the Fix Version unset or setting it to 2.3.1 or 2.4
> depending on the estimated time-scale of a resolution.
>
> BR,
>
> Jukka Zitting
Re: [jira] [Updated] (JCR-2887) Split PrivilegeRegistry in a
per-session manager instance and a repository level registry
Posted by Jukka Zitting <ju...@gmail.com>.
Hi Angela,
On Wed, Sep 28, 2011 at 8:40 AM, angela (Updated) (JIRA)
<ji...@apache.org> wrote:
> angela updated JCR-2887:
> ------------------------
>
> Fix Version/s: 2.3.0
I dropped the Fix Version from the issue since it wasn't yet fully
resolved in the 2.3.0 release candidate I cut yesterday. I'd recommend
either leaving the Fix Version unset or setting it to 2.3.1 or 2.4
depending on the estimated time-scale of a resolution.
BR,
Jukka Zitting
[jira] [Updated] (JCR-2887) Split PrivilegeRegistry in a
per-session manager instance and a repository level registry
Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2887:
-------------------------------
Fix Version/s: (was: 2.3)
2.4
Updated target version to 2.4 as the next stable release. Set to the next 2.3.x release if this gets resolved before 2.4 is branched.
> Split PrivilegeRegistry in a per-session manager instance and a repository level registry
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2887
> URL: https://issues.apache.org/jira/browse/JCR-2887
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.4
>
>
> in order to resolve the privilegeregistry related TODOs within jackrabbit-core, i would like to split off those
> methods from PrivilegeRegistry that are used on a per-session level (including jcr-names) and add them
> to a manager class that was present with each session context. consequently the responsibility of the
> registry was then limited to read/build the privilege definitions and would be present on the repositorycontext
> deprecating those methods that would be covered by the manager).
> in addition the naming was then consistent with what we use to have for nodetypes and namespaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-2887) Split PrivilegeRegistry in a
per-session manager instance and a repository level registry
Posted by "angela (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-2887:
------------------------
Fix Version/s: 2.3.0
> Split PrivilegeRegistry in a per-session manager instance and a repository level registry
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2887
> URL: https://issues.apache.org/jira/browse/JCR-2887
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.3.0
>
>
> in order to resolve the privilegeregistry related TODOs within jackrabbit-core, i would like to split off those
> methods from PrivilegeRegistry that are used on a per-session level (including jcr-names) and add them
> to a manager class that was present with each session context. consequently the responsibility of the
> registry was then limited to read/build the privilege definitions and would be present on the repositorycontext
> deprecating those methods that would be covered by the manager).
> in addition the naming was then consistent with what we use to have for nodetypes and namespaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (JCR-2887) Split PrivilegeRegistry in a
per-session manager instance and a repository level registry
Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-2887:
-------------------------------
Fix Version/s: (was: 2.3.0)
> Split PrivilegeRegistry in a per-session manager instance and a repository level registry
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2887
> URL: https://issues.apache.org/jira/browse/JCR-2887
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
>
> in order to resolve the privilegeregistry related TODOs within jackrabbit-core, i would like to split off those
> methods from PrivilegeRegistry that are used on a per-session level (including jcr-names) and add them
> to a manager class that was present with each session context. consequently the responsibility of the
> registry was then limited to read/build the privilege definitions and would be present on the repositorycontext
> deprecating those methods that would be covered by the manager).
> in addition the naming was then consistent with what we use to have for nodetypes and namespaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (JCR-2887) Split PrivilegeRegistry in a
per-session manager instance and a repository level registry
Posted by "angela (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved JCR-2887.
-------------------------
Resolution: Fixed
Fix Version/s: (was: 2.4)
2.3.5
resolving this issue fixed. the former PrivilegeRegistry has been split into
a per-session PrivilegeManager and a repository unique PrivilegeRegistry.
Those methods of PrivilegeRegistry that relied on Session-level namespace
mappings got deprecated. The corresponding methods on PrivilegeManager
should be used instead.
The new privilege manager is exposed as interface in
org.apache.jackrabbit.api.security.authorization.PrivilegeManager.
It provides methods to retrieve existing privileges and register new custom
privileges and aggregates of custom and built-in privileges. Registration of new
privileges works similar to namespace or node type registration as it requires
no Session.save() call and the new privileges are immediately effective on
the repository level.
Note however, that Jackrabbit internal permission evaluation does not take
custom privileges into account. Applications that want to make use of the access
control evaluation associated with custom privileges are in charge of the
corresponding validation. Up to now un-registration of custom privileges is
not supported.
The PrivilegeManager may be obtained by calling
JackrabbitWorkspace.getPrivilegeManager() which similar to Workspace#getNodeTypeManager() reflects the fact changes don't require a Session.save in order to be persisted.
In order to register custom privileges a given editing Session must be allowed
to manage privileges. This permission may be granted by editing the repository
level access control using a 'null' path (see also JCR-2774 for details).
> Split PrivilegeRegistry in a per-session manager instance and a repository level registry
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2887
> URL: https://issues.apache.org/jira/browse/JCR-2887
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.3.5
>
>
> in order to resolve the privilegeregistry related TODOs within jackrabbit-core, i would like to split off those
> methods from PrivilegeRegistry that are used on a per-session level (including jcr-names) and add them
> to a manager class that was present with each session context. consequently the responsibility of the
> registry was then limited to read/build the privilege definitions and would be present on the repositorycontext
> deprecating those methods that would be covered by the manager).
> in addition the naming was then consistent with what we use to have for nodetypes and namespaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JCR-2887) Split PrivilegeRegistry in a per-session
manager instance and a repository level registry
Posted by "angela (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela updated JCR-2887:
------------------------
Fix Version/s: 2.3.0
> Split PrivilegeRegistry in a per-session manager instance and a repository level registry
> -----------------------------------------------------------------------------------------
>
> Key: JCR-2887
> URL: https://issues.apache.org/jira/browse/JCR-2887
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core, security
> Reporter: angela
> Assignee: angela
> Fix For: 2.3.0
>
>
> in order to resolve the privilegeregistry related TODOs within jackrabbit-core, i would like to split off those
> methods from PrivilegeRegistry that are used on a per-session level (including jcr-names) and add them
> to a manager class that was present with each session context. consequently the responsibility of the
> registry was then limited to read/build the privilege definitions and would be present on the repositorycontext
> deprecating those methods that would be covered by the manager).
> in addition the naming was then consistent with what we use to have for nodetypes and namespaces.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira