jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-41) Initial repository setup
Date Mon, 01 Oct 2012 15:03:08 GMT

    [ https://issues.apache.org/jira/browse/OAK-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466864#comment-13466864
] 

Michael Dürig commented on OAK-41:
----------------------------------

Looks good to me in general. Some minor points:
* We should probably find a better name than {{DUMMY_PRINCIPAL}}. One that properly reflects
its intent.
* I think the 2nd FIXME in {{BuiltInNodeTypes.registerBuiltinNodeTypes}} can be removed.

What I'm not sure about is the security implications of this. Through {{Oak.createRoot()}}
everyone gets full access to the repository. While this might be intended, I think we should
document this at a broader scope: what and where are the security boundaries and how are they
enforced? It seems we are lacking a clear concept here (or at least a consensus thereof).

                
> Initial repository setup
> ------------------------
>
>                 Key: OAK-41
>                 URL: https://issues.apache.org/jira/browse/OAK-41
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core
>            Reporter: angela
>         Attachments: OAK-41-initial-proposal.patch
>
>
> upon the initial creation of a JCR repository the associated SPI layer (oak-core) should

> take care of setting up the corresponding MK-instance. this includes (incomplete list):
> - create the jcr repo (not sure what that means in terms of mk-implementation)
> - create the jcr:system node (unique for the repository, across workspaces) 
> - create the default workspace (-> name from config)
> - create the root node of the default workspace 
> in addition the repository would need to have access to the following
> information (maybe also mk-nodes underneath jcr:system ??)
> - built-in node types
> - built-in namespace
> - built-in privileges
> - built-in permissions
> - repository configuration (can that be stored in the mk?)
> as far as the workspace is concerned a functional repository would in 
> addition need to have:
> - build-in users (based on some sort of configuration)
> - workspace configuration

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message