[
https://issues.apache.org/jira/browse/SLING-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-827.
-----------------------------------
Resolution: Fixed
Replaced the <Security> element in the repository.xml file of the
jcr/jackrabbit-server module in Rev. 734085.
> Enable security configuration in default repository.xml
> -------------------------------------------------------
>
> Key: SLING-827
> URL: https://issues.apache.org/jira/browse/SLING-827
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.0.4
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Jackrabbit Server 2.0.4
>
>
> As discussed in [1] it would be a good idea to enable better access control
> in the default repository setup by using the DefaultSecurityManager,
> DefaultAccessManager and the DefaultLoginModule in the default repository.xml.
> The replacement <Security> element is:
> <Security appName="Jackrabbit">
> <SecurityManager
> class="org.apache.jackrabbit.core.DefaultSecurityManager"
> workspaceName="security">
> </SecurityManager>
> <AccessManager
> class="org.apache.jackrabbit.core.security.DefaultAccessManager">
> </AccessManager>
> <LoginModule
> class="org.apache.jackrabbit.core.security.authentication.DefaultLoginModule">
> <param name="anonymousId" value="anonymous"/>
> <param name="adminId" value="admin"/>
> </LoginModule>
> </Security>
> Note, that the DTD reference must also be increased to 1.5 to enable the
> SecurityManager element
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
