You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (Created) (JIRA)" <ji...@apache.org> on 2011/11/23 20:59:41 UTC
[jira] [Created] (SLING-2300) Add support to select the primary
workspace for authentication
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
Affects Versions: Auth Core 1.0.6
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: 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
[jira] [Commented] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156637#comment-13156637 ]
Felix Meschberger commented on SLING-2300:
------------------------------------------
Enhanced the DavEx AuthHttpContext.handleSecurity method to set the j_workspace request attribute to the workspace name extracted from the request URL in Rev. 1205779.
This request attribute is later taken into the AuthenticationInfo object by the AuthenticationInfoPostProcessor of the JCR Resource Resolver added in Rev. 1205633
> 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, JCR DavEx 1.0.0, Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0, JCR DavEx 1.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
[jira] [Commented] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Justin Edelson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200028#comment-13200028 ]
Justin Edelson commented on SLING-2300:
---------------------------------------
Felix - can this be marked as Resolved?
> 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, JCR DavEx 1.0.0, Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0, JCR DavEx 1.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
[jira] [Updated] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-2300:
-------------------------------------
Component/s: JCR
Affects Version/s: JCR Resource 2.0.10
Fix Version/s: JCR Resource 2.1.0
> 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
[jira] [Commented] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156336#comment-13156336 ]
Felix Meschberger commented on SLING-2300:
------------------------------------------
Added an AuthenticationInfoPostProcessor to ensure the user.jcr.workspace property in the authentication info to select the workspace for login in Rev. 1205633 (part of the JCR ResourceResolver bundle)
> 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
> Affects Versions: Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 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
[jira] [Resolved] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-2300.
--------------------------------------
Resolution: Fixed
Yes, this can be resolved
> 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, JCR DavEx 1.0.0, Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0, JCR DavEx 1.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
[jira] [Closed] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-2300.
-----------------------------------
> 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, JCR DavEx 1.0.0, Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0, JCR DavEx 1.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
[jira] [Updated] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-2300:
-------------------------------------
Affects Version/s: JCR DavEx 1.0.0
Fix Version/s: JCR DavEx 1.1.0
> 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, JCR DavEx 1.0.0, Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0, JCR DavEx 1.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
[jira] [Commented] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156294#comment-13156294 ]
Felix Meschberger commented on SLING-2300:
------------------------------------------
Fixing AuthenticationInfo post processing in Auth Core in Rev 1205605:
- AuthenticationInfo is always non-null -- for anon requests it just has null authentication type and the user name is either null or the configured anonymous user. This AuthenticationInfo can the be post processed and passed to the ResourceResolverFactory. This enables just setting the workspace name even for anonymous requests.
- The J_WORKSPACE constant is removed from AuthConstants again because Auth Core has nothing to do with workspaces
> 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
> Affects Versions: Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 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
[jira] [Commented] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156261#comment-13156261 ]
Felix Meschberger commented on SLING-2300:
------------------------------------------
Reconsidering the implementation: The Sling Authenticator does not know anything about workspaces. But the JCR Resource Resolver does and that one can provide an AuthenticationInfoPostProcessor which can inject the workspace property into the AuthenticationInfo based on the request attribute or parameter - or in the case of WebDAVEx even based on the request URL ...
> 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
> Affects Versions: Auth Core 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 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
[jira] [Commented] (SLING-2300) Add support to select the primary
workspace for authentication
Posted by "Felix Meschberger (Commented) (JIRA)" <ji...@apache.org>.
[ 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