[SLING-2300] Add support to select the primary workspace for authentication

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: JCR Resource 2.0.10, JCR DavEx 1.0.0, Auth Core 1.0.6
• Fix Version/s: JCR Resource 2.1.0, JCR DavEx 1.1.0, Auth Core 1.1.0
• Component/s: Authentication, JCR
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 23/Nov/11 19:58
• Updated: 18/May/12 07:46
• Resolved: 06/Feb/12 11:03

Description

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.