[jira] [Assigned] (SLING-2203) Allow for better configuration of sling home folder

[ https://issues.apache.org/jira/browse/SLING-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-2203: --- Assignee: Carsten Ziegeler (was: Felix Meschberger) > Allow for better configura

[jira] [Assigned] (SLING-2290) Updating a fragment with a different version but the same content does not work

[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-2290: --- Assignee: Carsten Ziegeler > Updating a fragment with a different version but the

[jira] [Updated] (SLING-2290) Updating a fragment with a different version but the same content does not work

[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-2290: Summary: Updating a fragment with a different version but the same content does not work (

[jira] [Created] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

Transient ResourceResolver bundle build failure on Linux Key: SLING-2296 URL: https://issues.apache.org/jira/browse/SLING-2296 Project: Sling Issue Type: Bug Components: JCR

[jira] [Commented] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

[ https://issues.apache.org/jira/browse/SLING-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154984#comment-13154984 ] Felix Meschberger commented on SLING-2296: -- Committed a fix in Rev. 1204886. This

[jira] [Resolved] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

[ https://issues.apache.org/jira/browse/SLING-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-2296. -- Resolution: Fixed The build failures are now fixed (thus the events are sent) and so th

RE: [RT] Improving access control

Okay, I might be a little bit late in the discussion... We're at MySign thought about such a access control layer in Sling a few months ago. Mainly because we do have different resource providers without the possibility of ACLs and also because some access rules can't be defined by ACLs (eg. acces

Re: [RT] Improving access control

Hi Mike, thanks for your valuable input! Yes, though we didn't talk about it, these checks should not only apply for reading but in general for all operations. I share the performance concern if a jcr node has to be checked twice as this would double the repository access per request. In genera

Jenkins build became unstable: sling-trunk-1.5 » Apache Sling Launchpad Testing WAR version #1449

See

Jenkins build became unstable: sling-trunk-1.5 » Apache Sling Launchpad Testing #1449

See

Jenkins build became unstable: sling-trunk-1.5 #1449

See

RE: [RT] Improving access control

> I share the performance concern if a jcr node has to be checked twice > as this would double the repository access per request. > > In general I think we can go with this (for reading): > 1. ResourceProvider delivers resource and maybe does already the ACL > check (like in the JCR case) > 2. Res

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1124

See

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1124

See

Jenkins build became unstable: sling-trunk-1.6 #1124

See

Re: [RT] Improving access control

On 22.11.11 11:15, "Mike Müller" wrote: >We're at MySign thought about such a access control layer in Sling a few >months ago. Mainly because we do have different resource providers >without the possibility of ACLs and also because some access rules >can't be defined by ACLs (eg. access from 8.00

Re: [RT] Improving access control

On Tue, Nov 22, 2011 at 1:45 PM, Alexander Klimetschek wrote: > ...Personally I think it is much better to put such additional ACL > implementations into the JCR (e.g. a custom Jackrabbit access control > provider). The problem is that anytime your code is using JCR (such as for > complex operatio

Re: [RT] Improving access control

This idea is about to provide a general approach for resource checking. Noone prevents you from doing a virtual tree in the jcr repository to check access of resources provided by other providers. But that's an implementation detail which I don't want to require upfront! Think in terms of our reso

[jira] [Created] (SLING-2297) JspScriptingTest.testChangingJsp failing

JspScriptingTest.testChangingJsp failing Key: SLING-2297 URL: https://issues.apache.org/jira/browse/SLING-2297 Project: Sling Issue Type: Bug Components: Scripting Affects Versions: Scri

Re: [RT] Improving access control

On Tue, Nov 22, 2011 at 2:17 PM, Carsten Ziegeler wrote: > This idea is about to provide a general approach for resource > checking >... > Think in terms of our resource abstraction - so far I don't see the > need to define any API to set/change/query these additional checks > within Sling. But t

Re: [RT] Improving access control

2011/11/22 Bertrand Delacretaz : > On Tue, Nov 22, 2011 at 1:45 PM, Alexander Klimetschek > wrote: >> ...Personally I think it is much better to put such additional ACL >> implementations into the JCR (e.g. a custom Jackrabbit access control >> provider). The problem is that anytime your code is u

Re: [RT] Improving access control

On Tue, Nov 22, 2011 at 2:43 PM, Vidar Ramdal wrote: > 2011/11/22 Bertrand Delacretaz : >> ...To keep things simple I'd suggest using a "shadow resource tree" in >> JCR if we need to define access control for ResourceResolvers which >> are not JCR: have the /SLING-ACL/resolvers/com.example.bar/foo

[jira] [Reopened] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

[ https://issues.apache.org/jira/browse/SLING-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened SLING-2296: -- The fix is not entirely correct: If the event is for a jar:content node and the resource i

[jira] [Commented] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

[ https://issues.apache.org/jira/browse/SLING-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155157#comment-13155157 ] Felix Meschberger commented on SLING-2296: -- Committed another fix in Rev. 1205007

Re: [RT] Improving access control

2011/11/22 Bertrand Delacretaz : > On Tue, Nov 22, 2011 at 2:17 PM, Carsten Ziegeler > wrote: >> This idea is about to provide a general approach for resource >> checking >>... >> Think in terms of our resource abstraction - so far I don't see the >> need to define any API to set/change/query the

[jira] [Resolved] (SLING-2296) Transient ResourceResolver bundle build failure on Linux

[ https://issues.apache.org/jira/browse/SLING-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-2296. -- Resolution: Fixed Looks like the issue is now fixed. Thus resolving this issue again.

[jira] [Resolved] (SLING-2297) JspScriptingTest.testChangingJsp failing

[ https://issues.apache.org/jira/browse/SLING-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-2297. -- Resolution: Cannot Reproduce After properly fixing SLING-2296 this issue goes away, too

[jira] [Resolved] (SLING-2290) Updating a fragment with a different version but the same content does not work

[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2290. - Resolution: Fixed Fix Version/s: Installer Core 3.2.4 Fixed in revision 1205016 -

[jira] [Created] (SLING-2298) Register web console plugin using a ServiceFactory

Register web console plugin using a ServiceFactory -- Key: SLING-2298 URL: https://issues.apache.org/jira/browse/SLING-2298 Project: Sling Issue Type: Improvement Components: Installe

Re: [RT] Improving access control

On 22.11.11 14:17, "Carsten Ziegeler" wrote: >This idea is about to provide a general approach for resource >checking. Noone prevents you from doing a virtual tree in the jcr >repository to check access of resources provided by other providers. >But that's an implementation detail which I don't w

Re: [RT] Improving access control

2011/11/22 Carsten Ziegeler : > This idea is about to provide a general approach for resource > checking. Noone prevents you from doing a virtual tree in the jcr > repository to check access of resources provided by other providers. > But that's an implementation detail which I don't want to requir

Re: [RT] Improving access control

2011/11/22 Vidar Ramdal : > 2011/11/22 Carsten Ziegeler : >> This idea is about to provide a general approach for resource >> checking. Noone prevents you from doing a virtual tree in the jcr >> repository to check access of resources provided by other providers. >> But that's an implementation det

RE: [RT] Improving access control

> 2011/11/22 Bertrand Delacretaz : > > On Tue, Nov 22, 2011 at 2:17 PM, Carsten Ziegeler > > wrote: > >> This idea is about to provide a general approach for resource > >> checking > >>... > >> Think in terms of our resource abstraction - so far I don't see the > >> need to define any API to set/

Re: [RT] Improving access control

On Tue, Nov 22, 2011 at 4:39 PM, Carsten Ziegeler wrote: > 2011/11/22 Vidar Ramdal : >>... I'm coming late to this party, but having read the thread I'm not sure >> if the proposal is about a) specifying access control APIs to be >> implemented by resource providers, or b) implement access control

[jira] [Resolved] (SLING-2298) Register web console plugin using a ServiceFactory

[ https://issues.apache.org/jira/browse/SLING-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-2298. - Resolution: Fixed Changed in revision 1205052 > Register web console plu

Re: [RT] Improving access control

2011/11/22 Bertrand Delacretaz : > On Tue, Nov 22, 2011 at 4:39 PM, Carsten Ziegeler > wrote: >> 2011/11/22 Vidar Ramdal : >>>... I'm coming late to this party, but having read the thread I'm not sure >>> if the proposal is about a) specifying access control APIs to be >>> implemented by resource

Jenkins build is back to stable : sling-trunk-1.5 » Apache Sling Launchpad Testing #1450

See

Jenkins build is back to stable : sling-trunk-1.5 » Apache Sling Launchpad Testing WAR version #1450

See

Jenkins build is back to stable : sling-trunk-1.5 #1450

See

[jira] [Commented] (SLING-2290) Updating a fragment with a different version but the same content does not work

[ https://issues.apache.org/jira/browse/SLING-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155279#comment-13155279 ] Carsten Ziegeler commented on SLING-2290: - Thanks Konrad for your test case!

Re: [RT] Improving access control

Hi all, Bertrand asked what user interface we could use to configure an access control provider. We could do some wiring based on an osgi property, if it exists, using an scr annotation on the resource provider to specify the service which implements the access control gate (if one is not provide

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1125

See

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #1125

See

Jenkins build is back to stable : sling-trunk-1.6 #1125

See

Build failed in Jenkins: sling-contrib-1.5 #767

See -- [...truncated 3002 lines...] [INFO] Copying bundle from /home/jenkins/.m2/repository/org/apache/sling/org.apache.sling.scripting.scala.hello-world/0.9.0-SNAPSHOT/org.apache.sling.scripting.scala.

Re: [RT] Improving access control

On Tue, Nov 22, 2011 at 6:37 PM, Sarwar Bhuiyan wrote: > ...Bertrand asked what user interface we could use to configure an access > control provider... Sorry, my question was badly phrased: what I meant is that people already need to have a UI to configure JCR access control - if this new featur

Re: [RT] Improving access control

In any case, setting the scr property to specify the access control service/class still holds as it allows us to set an initial value using scr annotations and also we can reuse or reconfigure access control provider for each resource provider. Just an idea instead of making the resource provider

Re: [RT] Improving access control

But again the question (as asked by me and Vidar): why does Sling need that? What is wrong with a resource provider simply not returning resources where the user has no access, as it is already the case with the JCR provider? Cheers, Alex -- Alexander Klimetschek Developer // Adobe (Day) // Ber

[jira] [Updated] (SLING-2136) Sling POST Servlet: Configuration of Allowed Paths

[ https://issues.apache.org/jira/browse/SLING-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra updated SLING-2136: Attachment: post_servlet_filter-1205238.patch Patch that introduces a new configuration for

Re: [RT] Improving access control

Hi, I fear the same, that sling tries to re-define and re-implement the whole JCR API stack (it already does for the most part :-(. Initially sling was a framework for building web application on top a JCR repository. But now it's a framework that happens to integrate nicely on JCR. I think the div

RE: [RT] Improving access control

I think the discussion here is missunderstood. It's neither about to redefine existing ACLs nor about reinventing something already existing. It's just about introducing hooks or entrypoint to let developers define some other access controlling rules if needed. Sling will NOT have to deal with perm