To solve the issue, check the following things
1. Any Repository Policy nodes that have security settings specified at the root level (/) which can restrict anonymous access.
2. If anonymous user has appropriate ACL’s assigned on the node being accessed and redirected to in case applicable.
3. Check and see in your publish environment (http://localhost:4503/system/console/configMgr) if you have enabled anonymous access to the user in Apache Sling Authentication Service. There is a checkbox, just check that.
These are some of the possible causes of the user being redirected to the login page. I would like to hear from the community in case anybody else also solved their problem with other solutions.
No comments:
Post a Comment
If you have any doubts or questions, please let us know.