Re: Preventing Listing of child nodes of a resource.

On 6 Jul 2010, at 22:15, Alexander Klimetschek wrote: > You would not have an anonymous user here at all, as you'd enforce > authentication for the /_user tree. Unfortunately that does not work. /_user//** *must* be accessible by anon so we cant force authentication. Without differentiation

Re: Preventing Listing of child nodes of a resource.

On Wed, Jul 7, 2010 at 09:45, Ian Boston wrote: > > On 6 Jul 2010, at 22:15, Alexander Klimetschek wrote: > >> You would not have an anonymous user here at all, as you'd enforce >> authentication for the /_user tree. > > > Unfortunately that does not work. > > /_user//** > > *must* be accessible b

Hudson build is back to stable : sling-trun k-1.6 » Apache Sling Launchpad Testing #473

See

Hudson build is back to stable : sling-trunk-1.6 #473

See

Re: Preventing Listing of child nodes of a resource.

On 7 Jul 2010, at 12:33, Alexander Klimetschek wrote: > On Wed, Jul 7, 2010 at 09:45, Ian Boston wrote: >> >> On 6 Jul 2010, at 22:15, Alexander Klimetschek wrote: >> >>> You would not have an anonymous user here at all, as you'd enforce >>> authentication for the /_user tree. >> >> >> Unfor

Re: Preventing Listing of child nodes of a resource.

On 7/7/10 8:46 AM, Ian Boston wrote: >>> Without differentiation between "list child nodes" and "read child node" in >>> jcr-170 or jcr-283, I don't think what I need to be done, can be achieved >>> by any access manager/access control provider that conforms to the standard. >>> >>> So I have no

Unified authentication/authorization in Sling? [WAS: Preventing Listing of child nodes of a resource.]

On Thu, Jul 1, 2010 at 1:52 PM, Ian Boston wrote: > Hi, > I want to be able to stop the listing of all child nodes at specific urls, > but still allow direct access to items in a subtree. Not really related to Ian's post at all, but it got me thinking: Sling currently implements a way authentica

Re: Preventing Listing of child nodes of a resource.

On 7 Jul 2010, at 14:16, Justin Edelson wrote: > IIUC the number of child nodes isn't relevant. If you broke down the > children of /users to /users/a, /users/b, /users/c ... /users/z, you > STILL wouldn't want to allow the children of those nodes to be listed. Yes thats right, no listing or dis

Re: Preventing Listing of child nodes of a resource.

On Wed, Jul 7, 2010 at 14:46, Ian Boston wrote: >> 1) the public part would be some subdirectory of the user node, ie. >> /_user//public_html; then with a principal-based ACL like >> "read anon /_user/*/public_html" it should be accessible to the >> public; a special filter would then do the redir

Re: Preventing Listing of child nodes of a resource.

On 7 Jul 2010, at 14:25, Alexander Klimetschek wrote: >> That would allow listing of all the users. > > Ah, right, now I am finally getting to the point of this discussion ;-). Thats probably down to my poor explanation, sorry. > > In this case I would give the /content/users node an explicit

Build failed in Hudson: sling-contrib-1.5 #515

See -- [...truncated 2027 lines...] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.ref

change versioning scheme for gwt contrib module

I'd like to release the contrib/gwt/servlet module, but have some misgivings about the versioning scheme used there. Currently, the version of this module is the same as the underlying GWT version. So currently, it is 2.0.3-SNAPSHOT. However, this goes against our overall versioning principals and

Re: change versioning scheme for gwt contrib module

On 7 Jul 2010, at 16:26, Justin Edelson wrote: > I'd like to release the contrib/gwt/servlet module, but have some > misgivings about the versioning scheme used there. > > Currently, the version of this module is the same as the underlying GWT > version. So currently, it is 2.0.3-SNAPSHOT. Howev

Re: change versioning scheme for gwt contrib module

On 7/7/10 11:55 AM, Ian Boston wrote: > > On 7 Jul 2010, at 16:26, Justin Edelson wrote: > >> I'd like to release the contrib/gwt/servlet module, but have some >> misgivings about the versioning scheme used there. >> >> Currently, the version of this module is the same as the underlying GWT >> ve

[jira] Commented: (SLING-1549) Servlet cache can grow infinitely

[ https://issues.apache.org/jira/browse/SLING-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886044#action_12886044 ] Andrew Khoury commented on SLING-1549: -- I think that using a cache size limit along wi

Build failed in Hudson: sling-trunk-1.6 #474

See Changes: [justin] SLING-1447 - fixing relative copy/move path to remove workspace if necessary [justin] SLING-1448 - removing unused constant -- [...truncated 6738 lines...] Test

Build failed in Hudson: sling-contrib-1.5 #516

See -- [...truncated 3710 lines...] [INFO] Building Apache Sling Features for ServiceMix Kernel [INFO]task-segment: [clean, install] [INFO] ---

[jira] Commented: (SLING-1549) Servlet cache can grow infinitely

[ https://issues.apache.org/jira/browse/SLING-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886252#action_12886252 ] Carsten Ziegeler commented on SLING-1549: - Yes, I completly agree. If someone could