You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Vidar S. Ramdal (JIRA)" <ji...@apache.org> on 2009/04/24 01:09:30 UTC

[jira] Resolved: (SLING-880) Pluggable AccessManager

     [ https://issues.apache.org/jira/browse/SLING-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vidar S. Ramdal resolved SLING-880.
-----------------------------------

    Resolution: Fixed

Tidied the patch up a bit, added license headers, and applied it in rev#768086

> Pluggable AccessManager
> -----------------------
>
>                 Key: SLING-880
>                 URL: https://issues.apache.org/jira/browse/SLING-880
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>    Affects Versions: JCR Jackrabbit Server 2.0.2
>            Reporter: Vidar S. Ramdal
>            Assignee: Vidar S. Ramdal
>             Fix For: JCR Jackrabbit Server 2.0.4
>
>         Attachments: SLING-880.patch
>
>
> Provide a way to plug in a custom AccessManager, just as you can plug in a custom LoginModule or AuthenticationPlugin, using a delegate. This way we don't have to export the jackrabbit.core packages.
> See http://markmail.org/thread/wlqm3yjpbyokwcvy and http://markmail.org/thread/myaieenaelot4y66 for background.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.