sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konrad Windszus <konra...@gmx.de>
Subject Re: Minimum JCR access rights for a path-based Sling servlet
Date Mon, 19 Feb 2018 17:08:32 GMT
Sorry for the noise, actually no right is necessary as correctly stated in the wiki. I had
an issue with the user provisioning process.
Konrad

> On 19. Feb 2018, at 18:01, Konrad Windszus <konrad_w@gmx.de> wrote:
> 
> Although it is currently stated at https://sling.apache.org/documentation/the-sling-engine/servlets.html#caveats-when-binding-servlets-by-path
<https://sling.apache.org/documentation/the-sling-engine/servlets.html#caveats-when-binding-servlets-by-path>
that no JCR repository acls are evaluated when accessing a servlet registered by path I always
get back a 401 when trying to access such a servlet with an unprivileged user. Is there some
minimum repository right being evaluated beforehand (i.e. by a servlet filter or the Sling
Main Servlet somehow?).
> Thanks for your input,
> Konrad
> 


Mime
View raw message