[ https://issues.apache.org/jira/browse/OAK-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466872#comment-13466872 ]
Jukka Zitting commented on OAK-41: ---------------------------------- This kind of initialization should IMHO be complete outside the scope of authorization. If the installation of built-in node types has to go through access control checks, we're doing something wrong. For example, there should be no need for {{Oak.createRoot()}} as long as a repository created with {{Oak.createContentRepository()}} comes with no default authentication or authorization components (which unfortunately is currently not the case). Then the {{Oak.createRoot()}} operation can simply be expressed as {{contentRepository.login(null, null)}}. > 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