Getting 403 Forbidden Error when running reports on publish instance | Community
Skip to main content
GK-007
GK-007
Level 9
February 7, 2017
Solved

Getting 403 Forbidden Error when running reports on publish instance

  • February 7, 2017
  • 4 replies
  • 3570 views

Hi All,

We have implemented reports using AEM in built framework,we are able to run the utility without any issue in author instance but when we try to run from publish we are getting 403 Forbidden Error.

I have performed below work-around to run the report but still getting same error.

1. Logged in as admin and have run the report

2.Removed POST method from Apache Sling Referrer Filter configuration and have run the report.

If anyone has come across the same issue,please help me in this regard.

Thanks,

Kishore

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by GK-007

Issue is fixed after removing the 'POST' method for Filter Methods property in Apache Granite CSRF Filter configuration.

4 replies

sandeepm744005
sandeepm744005
Level 5
February 8, 2017

Hi Kishore, sounds like issue with permissions only, for the workaround, can you try providing the "everyone" group access to "/etc/reports".

GK-007
GK-007Author
Level 9
February 8, 2017

i still see same issue.

ERROR: POST /apps/tools/components/xxxxxx/run.html HTTP/1.1] com.adobe.granite.csrf.impl.CSRFFilter doFilter: the provided CSRF token is invalid

Strange thing is we are unable to run this on local publish instance and getting the same issue.

sandeepm744005
sandeepm744005
Level 5
February 8, 2017

Are you trying to access reports using dispatcher ? if yes, then make sure that, you are passing "CSRF-Token" in the header.

Refer this url which is related to the exception which you are getting. Hope it helps.

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__14yg-a_form_thatpostsda.html

GK-007
GK-007AuthorAccepted solution
Level 9
February 8, 2017

Issue is fixed after removing the 'POST' method for Filter Methods property in Apache Granite CSRF Filter configuration.

Terms & ConditionsAccessibility statement

Loading footer...