Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

On 24 November 2011 18:23, Carsten Ziegeler wrote: > 2011/11/23 Alexander Klimetschek : >> On 23.11.11 12:57, "Vidar Ramdal" wrote: >>>2011/11/23 Tobias Bocanegra : I would rather put effort in creating connectors in jackrabbit. So having a LDAP, noSQL, etc. mapped into JCR brings much

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

2011/11/23 Alexander Klimetschek : > On 23.11.11 12:57, "Vidar Ramdal" wrote: >>2011/11/23 Tobias Bocanegra : >>> I would rather put effort in creating connectors in jackrabbit. So >>> having a LDAP, noSQL, etc. mapped into JCR brings much more value and >>> having them on the resource level. >> >

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

See

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

See

Bootstrap config files.

Hi, Is there a standard way in the Sling bootstrap of allowing both the bootstrap and bundles to place files under Sling Home, in the same way that the content importer transfers resources from a jar into JCR ? Is it something that would be acceptable to the project, or is it an OSGi anti-pattern

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

See

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

On 23.11.11 12:57, "Vidar Ramdal" wrote: >2011/11/23 Tobias Bocanegra : >> I would rather put effort in creating connectors in jackrabbit. So >> having a LDAP, noSQL, etc. mapped into JCR brings much more value and >> having them on the resource level. > >Out of curiosity, for what reasons? Becau

[jira] [Commented] (SLING-2300) Add support to select the primary workspace for authentication

[ 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 ens

[jira] [Updated] (SLING-2300) Add support to select the primary workspace for authentication

[ 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: J

[jira] [Commented] (SLING-2300) Add support to select the primary workspace for authentication

[ 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 AuthenticationInfoPostProces

[jira] [Commented] (SLING-2300) Add support to select the primary workspace for authentication

[ 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 proces

[jira] [Commented] (SLING-2300) Add support to select the primary workspace for authentication

[ 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

[jira] [Resolved] (SLING-2280) Add support for non-browser authentication

[ https://issues.apache.org/jira/browse/SLING-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-2280. -- Resolution: Fixed So this can be resolved again. > Add support for non

[jira] [Commented] (SLING-2299) Consolidate constants and utility methods

[ https://issues.apache.org/jira/browse/SLING-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156249#comment-13156249 ] Felix Meschberger commented on SLING-2299: -- Same for RedirectOnLoginErrorTest: fi

[jira] [Commented] (SLING-2280) Add support for non-browser authentication

[ https://issues.apache.org/jira/browse/SLING-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156247#comment-13156247 ] Felix Meschberger commented on SLING-2280: -- Same for RedirectOnLoginErrorTest: Ca

[jira] [Commented] (SLING-2299) Consolidate constants and utility methods

[ https://issues.apache.org/jira/browse/SLING-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156246#comment-13156246 ] Felix Meschberger commented on SLING-2299: -- AuthenticationResponseCode tests fail

[jira] [Commented] (SLING-2280) Add support for non-browser authentication

[ https://issues.apache.org/jira/browse/SLING-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156245#comment-13156245 ] Felix Meschberger commented on SLING-2280: -- Actually the AuthenticationResponseCo

[jira] [Reopened] (SLING-2280) Add support for non-browser authentication

[ https://issues.apache.org/jira/browse/SLING-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened SLING-2280: -- This change causes some integration tests to break which don't expect the new behavior of

[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

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

See

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

See

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

See

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

See

[jira] [Commented] (SLING-2299) Consolidate constants and utility methods

[ https://issues.apache.org/jira/browse/SLING-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155925#comment-13155925 ] Felix Meschberger commented on SLING-2299: -- Fixed uses of AuthUtil.checkReferer i

[jira] [Commented] (SLING-2299) Consolidate constants and utility methods

[ https://issues.apache.org/jira/browse/SLING-2299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155923#comment-13155923 ] Felix Meschberger commented on SLING-2299: -- Implemented this consolidation in Rev

[jira] [Created] (SLING-2299) Consolidate constants and utility methods

Consolidate constants and utility methods - Key: SLING-2299 URL: https://issues.apache.org/jira/browse/SLING-2299 Project: Sling Issue Type: Improvement Components: Authentication Affects

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

See -- [...truncated 3001 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

Hi, Am 23.11.2011 um 14:01 schrieb Bertrand Delacretaz: > On Wed, Nov 23, 2011 at 9:41 AM, Felix Meschberger wrote: >> ...I suggest, we extend the Resource API as follows: >> >> boolean ResourceResolver.hasPermission(String absPath, String action); >> boolean ResourceProvider.hasPermission(

Re: [RT] Improving access control

On Wed, Nov 23, 2011 at 9:41 AM, Felix Meschberger wrote: > ...I suggest, we extend the Resource API as follows: > >   boolean ResourceResolver.hasPermission(String absPath, String action); >   boolean ResourceProvider.hasPermission(String absPath, String action); > >... > In addition, we would de

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

> On Wed, Nov 23, 2011 at 11:10 AM, Vidar Ramdal > wrote: >> 2011/11/23 Carsten Ziegeler : >>> I know that some people have developed such things but don't want to >>> contribute them (which is totally fine). I'm planning to work on such >>> providers in the near future. If others are interested

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

2011/11/23 Vidar Ramdal : > 2011/11/23 Carsten Ziegeler : >> I know that some people have developed such things but don't want to >> contribute them (which is totally fine). I'm planning to work on such >> providers in the near future. If others are interested to use their >> favorite data storage

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

On Wed, Nov 23, 2011 at 11:10 AM, Vidar Ramdal wrote: > 2011/11/23 Carsten Ziegeler : >> I know that some people have developed such things but don't want to >> contribute them (which is totally fine). I'm planning to work on such >> providers in the near future. If others are interested to use th

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

2011/11/23 Carsten Ziegeler : > I know that some people have developed such things but don't want to > contribute them (which is totally fine). I'm planning to work on such > providers in the near future. If others are interested to use their > favorite data storage with Sling, I'm happy to apply c

Re: Providers for non-JCR data storage? (was: [RT] Improving access control)

Hi, I know that some people have developed such things but don't want to contribute them (which is totally fine). I'm planning to work on such providers in the near future. If others are interested to use their favorite data storage with Sling, I'm happy to apply contributions or discuss the best

[jira] [Resolved] (SLING-1289) Additional ScriptSelectionTest case

[ https://issues.apache.org/jira/browse/SLING-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1289. - Resolution: Fixed Fix Version/s: Servlets Resolver 2.1.2 Thanks for your patch, Ju

Re: [RT] Improving access control

2011/11/23 Vidar Ramdal : > 2011/11/23 Mike Müller : >> 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 c

Re: [RT] Improving access control

2011/11/23 Mike Müller : > 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. > Sl

[jira] [Assigned] (SLING-1289) Additional ScriptSelectionTest case

[ https://issues.apache.org/jira/browse/SLING-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-1289: --- Assignee: Carsten Ziegeler > Additional ScriptSelectionTest case > --

Re: [RT] Improving access control

Hi, Sorry, too, for being late at the party ... I think we should * keep it simple * not try to duplicate existing stuff * ensure consistency Thus, I think the Sling Resource API should not impose another layer of access control checks to what is already implemented in ResourceProvider impl

Providers for non-JCR data storage? (was: [RT] Improving access control)

On Wed, Nov 23, 2011 at 9:27 AM, Carsten Ziegeler wrote: > ...And keep in mind that the intend of Sling is to provide a framework to > create a resource oriented architecture. This is not tied to jcr. We > already have other providers (file and bundle) and in the near future > we will have additio

Re: [RT] Improving access control

On Wed, Nov 23, 2011 at 9:27 AM, Carsten Ziegeler wrote: > 2011/11/23 Mike Müller : >> I think the discussion here is missunderstood. It's neither about >> to redefine existing ACLs nor about reinventing something already >> existing... Well, this thread's subject says "improving access control"

Re: [RT] Improving access control

2011/11/23 Mike Müller : > 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. > Sl