jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2419) WorkspaceAccessManager defined with SecurityManager that keeps users per workspace must test if user exists
Date Wed, 02 Dec 2009 10:36:21 GMT

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

angela resolved JCR-2419.
-------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-beta4
         Assignee: angela

> WorkspaceAccessManager defined with SecurityManager that keeps users per workspace must
test if user exists
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-2419
>                 URL: https://issues.apache.org/jira/browse/JCR-2419
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.0-beta4
>
>
> the WorkspaceAccessManager defined with the security manager keeping users per workspace
currently returns true upon calls to grant(Set, String) if
> a workspace with the given name exists.
> while this is fine for the initial check upon session creation, it obviously isn't for
all method calls that test for accessible workspace names, such as
> Workspace#getAccessibleWorkspaceName, Workspace#clone and copy across workspaces.
> instead it should test if any of the specified principals corresponds to a valid user
within the workspace identified by the given workspaceName.

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


Mime
View raw message