Anonymous user requires read access to config in order to display pages on
public instance
------------------------------------------------------------------------------------------
Key: MAGNOLIA-1605
URL: http://jira.magnolia.info/browse/MAGNOLIA-1605
Project: Magnolia
Issue Type: Bug
Environment: 3.1-SNAPSHOT
Reporter: Amir Mistric
Assigned To: Boris Kraft
AggregatorFilter redericets to a 404 error when anonymous user tries to access
the public instance.
However, after logging into the public instance the pages show without any
problems.
After debugging this with Sameer, we noticed that giving anonymous role a read
only access to CONFIG repo resolves the issue; however this is not the right
solution since anonymous role should not have any access to config repo.
- workaround:
-- add read only access to anonymous role on config repo
- "easy" fix:
-- change the anonymous role public bootstrap file to contain the above fix
- correct solution:
-- looks like access in filters is done using Magnolia Context which checks
permissions and has a misleading error (404 instead of ???)...Perhaps System
Context should be used if no side effects exist.
Sameer has seen this issue as it occurs (using web ex) and is familiar with it.
Regards
Amir
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
