[
https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731925#comment-13731925
]
Carsten Ziegeler commented on SLING-2944:
-----------------------------------------
Right - I think the point is to be able to configure this without a specific
packaging (bundling) of services - so we rather want to configure this based on
a service than on a bundle - as the service might move from one bundle to
another. Unfortunately we only get support for the client bundle through a
ServiceFactory. On the other hand we can't rely alone on a service identifier
(comparable to the PID) as this would be open to the same "attack" as the
additional header.
So the only thing which is quiet safe to use is the bundle symbolic name as we
have it right now.
I think it's better to be a little bit safer with the burden of potentially
more configuration if sub services spread across bundles. So I would remove the
header
> Replace administrative login by service-based login
> ---------------------------------------------------
>
> Key: SLING-2944
> URL: https://issues.apache.org/jira/browse/SLING-2944
> Project: Sling
> Issue Type: New Feature
> Components: API, JCR, ResourceResolver, Service User Mapper
> Affects Versions: JCR Resource 2.2.8, JCR Jackrabbit Server 2.1.0, JCR
> Base 2.1.2, JCR API 2.1.0, API 2.4.2, Resource Resolver 1.0.6
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Service User Mapper 1.0.0, Servlets Resolver 2.2.6, JCR
> Resource 2.3.0, JCR Jackrabbit Server 2.2.0, JCR Base 2.1.4, JCR API 2.2.0,
> File System Resource Provider 1.1.4, Extensions Bundleresource 2.1.4, API
> 2.5.0, Resource Resolver 1.1.0
>
> Attachments: serviceusermapper.tgz, SLING-2944.patch
>
>
> From the start Sling tried to solve the problem of providing services access
> to the repository and resource tree without having to hard code and configure
> any passwords. This was done first with the
> SlingRepository.loginAdministrative and later with the
> ResourceResolverFactory.getAdministrativeResourceResolver methods.
> Over time this mechanism proved to be the hammer to hit all nails.
> Particularly these methods while truly useful have the disadvantage of
> providing full administrative privileges to services where just some specific
> kind of privilege would be enough.
> For example for the JSP compiler it would be enough to be able to read the
> JSP source scripts and write the Java classes out to the JSP compiler's
> target location. Other access is not required. Similarly to manage users user
> management privileges are enough and no access to /content is really required.
> To solve this problem a new API for Service Authentication has been proposed
> at https://cwiki.apache.org/confluence/display/SLING/Service+Authentication.
> The prototype of which is implemented in
> http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/deprecate_login_administrative.
> This issue is about merging the prototype code back into trunk and thus fully
> implementing the feature.
--
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
