[
https://issues.apache.org/jira/browse/SLING-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594907#action_12594907
]
Felix Meschberger commented on SLING-426:
-----------------------------------------
There was a bug in the configuration definition for the Authenticator (see
SLING-432), which might cause confusion:
The actual default value for "Allow Anonymous Access" is "true". The default
value for this setting as displayed in the Configuration Admin Screen is
"false" though.
So if you were instructed to go to the configuration screen to switch the thing
off, you were thinking, "hey, this is already switched off, what is going
on....".
Your short-term fix would be to just press "Save" here to store what is
displayed. This really switches anonymous access off.
The discrepancy between actual and displayed default value has been fixed as
per SLING-432.
Thanks for reporting.
> Sling client library tests: Allow Anonymous Access configuration on
> Authentication Filter does not take effect.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SLING-426
> URL: https://issues.apache.org/jira/browse/SLING-426
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Environment: Windows
> Reporter: Paul Noden
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: 2.0.0
>
>
> In the latest version I found that checking the Allow Anonymous Access
> configuration on Authentication Filter does not take effect.
> Changing the anonymous user/password for the Embedded JCR Repository to
> admin:admin was the only way I got the Sling client library tests
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
