[ 
https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156344#comment-13156344
 ] 

Felix Meschberger commented on SLING-2300:
------------------------------------------

Rev. 1205635 Integration tests to ensure the workspace AuthenticationInfo post 
processor properly works (need a component to create some test workspaces and a 
test itself to login to those workspaces)

Updated required dependencies for the JCR Resource Resolver bundle in Rev. 
1205638 and the Launchpad Test Services bundle in Rev. 1205636
                
> Add support to select the primary workspace for authentication
> --------------------------------------------------------------
>
>                 Key: SLING-2300
>                 URL: https://issues.apache.org/jira/browse/SLING-2300
>             Project: Sling
>          Issue Type: New Feature
>          Components: Authentication, JCR
>    Affects Versions: JCR Resource 2.0.10, Auth Core 1.0.6
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: JCR Resource 2.1.0, Auth Core 1.1.0
>
>
> The JCR based ResourceResolverFactory supports selecting the Workspace to 
> which a session should be created by specifying the user.jcr.workspace 
> property of the credentials map. Currently the Sling authenticator does not 
> support feeding that property from a request.
> To fully support certain use cases -- particularly WebDAV which accesses 
> different workspaces through the URL space (e.g. /server/wsp1/content 
> accesses the /content item on the "wsp1" workspace through WebDAVEx) -- the 
> Sling Authenticator should support accessing select workspaces directly.
> This can be indicated by a j_workspace request parameter or request 
> attribute. The request attribute case can be used by the WebDAVEx bundle to 
> extract the workspace name from the URL and feed the attribute for 
> authentication.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to