Hi,
On Thu, Mar 12, 2020 at 7:25 AM Oliver Lietz wrote:
> On Wednesday, March 11, 2020 10:05:20 PM CET Cris Rockwell wrote:
> > ...I am asking why this default exists.
> > Is there is a rationale for the default or no?...
> It is convenient for the Sling Starter and the sample applications...
I
On Wednesday, March 11, 2020 10:05:20 PM CET Cris Rockwell wrote:
> I think your response helps in a way. I am asking why this default exists.
> Is there is a rationale for the default or no? Based on your response, it
> should be deleted if the application needs to control ACL read permissions,
>
I think your response helps in a way. I am asking why this default exists. Is
there is a rationale for the default or no? Based on your response, it should
be deleted if the application needs to control ACL read permissions, and maybe
there is no reason for the default other than to ensure every
On Wednesday, March 11, 2020 8:34:12 PM CET Cris Rockwell wrote:
> Hi Oliver
>
> Thanks for the fast reply. Can I ask the exact same set of questions about
> default jcr:read access for everyone on /content? Is that required?
It depends on your application. If you do not want to serve content to
Hi Oliver
Thanks for the fast reply. Can I ask the exact same set of questions about
default jcr:read access for everyone on /content? Is that required?
Cris Rockwell
Applications Architect Sr
College of Literature, Science, and the Arts | University of Michigan
LSA Technology Services | 6503
On Wednesday, March 11, 2020 6:50:51 PM CET Cris Rockwell wrote:
> Hello Sling Users
Hi Cris,
> When I launch Sling, there is an ACL for jrc:read for the everyone
> ‘principle' on jcr:root, as described in the repoinit.txt
> http://archive.apache.org/dist/sling/org.apache.sling.launchpad-9.jar
>
