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

Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/09/20 17:45:52 UTC

[jira] [Resolved] (OAK-1028) Pass Subject directly to the permission validator

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

Jukka Zitting resolved OAK-1028.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.10

Done in revision 1524828.
                
> Pass Subject directly to the permission validator
> -------------------------------------------------
>
>                 Key: OAK-1028
>                 URL: https://issues.apache.org/jira/browse/OAK-1028
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.10
>
>
> Currently we're using the JAAS AccessContext mechanism to pass the current Subject to the permission validator. That solution was used to avoid having to pass extra arguments along with the change set through the whole stack.
> Since then however we introduced the mechanism by which extra commit hooks can be associated with individual commits, and we already use that mechanism to pass the workspace name to the permission validator.
> We could use the same thing also for the Subject, and thus avoid the more complex ThreadLocal-based AccessContext setup.

--
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