[
https://issues.apache.org/jira/browse/SLING-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462425#comment-16462425
]
Bertrand Delacretaz commented on SLING-7647:
--------------------------------------------
The failing (trunk) log has
{code}
org.apache.jackrabbit.oak.spi.security.authentication.AbstractLoginModule
Login: Credentials 'javax.jcr.GuestCredentials@6938bd73' obtained from callback
...
org.apache.sling.jcr.resource.internal.helper.jcr.JcrItemResourceFactory
createResource: No JCR Item exists at path '/tmp/test1234'
{code}
Which seems to indicate that it's Oak which is rejecting access to the
{{/tmp/test1234}} node for the {{GuestCredentials}} user.
At the same point, the sling10 log says {{Found JCR Node Resource at path
'/tmp/test1234'}}.
> Anonymous access to content stopped working
> -------------------------------------------
>
> Key: SLING-7647
> URL: https://issues.apache.org/jira/browse/SLING-7647
> Project: Sling
> Issue Type: Bug
> Components: Authentication
> Reporter: Bertrand Delacretaz
> Priority: Major
> Labels: sling-IT
> Attachments: sling10-get-request.txt, trunk-get-request.txt
>
>
> Looking at SLING-7636 and especially the {{AnonymousAccessTest}} shows that
> anonymous access stopped working. The following scenario works with the
> sling10 jar but not with the current trunk:
> {code}
> curl -u admin:admin -Ftitle=test http://localhost:8080/tmp/test1234
> curl -u admin:admin http://localhost:8080/tmp/test1234.json
> curl http://localhost:8080/tmp/test1234.tidy.json
> {code}
> With sling10 the last request gets content, while with the current trunk it
> gets a 404.
> I'll attach the logs of that last request on both versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
