Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM 6.4.8.1 (CFP 1) and POST Requests

cecheta
Level 2
Level 2

I have an HTML form inside an iframe that makes a POST request to an AEM servlet. The servlet path is excluded by the Adobe Granite CSRF Filter, and the host making the POST request has been added to the Allowed Hosts in the Apache Sling Referrer Filter. On AEM 6.4.8.0, everything works fine, however when upgrading to 6.4.8.1, the POST request returns a 403 Forbidden response. This is on an Author instance. The following message is seen in the Error log after making the request:

 

*INFO* [qtp691096566-2507] org.apache.sling.auth.core.impl.SlingAuthenticator getAnonymousResolver: Anonymous access not allowed by configuration - requesting credentials

 

How can I avoid this so the POST request is successful?

6.4.8.1
1 Accepted Solution
kunal23
Correct answer by
Level 10
Level 10

Don't do any changes to white list the host or allow anonymous requests. It is not a recommended option and is not best security practice. You can solve your problem by including CSRF framework clientlib on the page where you have created your form. ClientLib category is -  granite.csrf.standalone

More details - https://helpx.adobe.com/experience-manager/6-2/sites/developing/using/csrf-protection.html

View solution in original post

7 Replies
vanegi
Employee
Employee

Hi @cecheta,

Have you tried checking the "Allow anonymous" in Apache Sling Authentication Service config?

 

Capture.JPG

 

Thanks!!

BrianKasingli
Community Advisor
Community Advisor

@cecheta,

Try @vanegi's trick, "Allow anonymous", if that does not work, you can try to send a  request header:

Authorization Basic YWRtaW46YWRtaW4=

 

ChitraMadan
Community Advisor
Community Advisor

Hi @cecheta ,

 

If you are testing this on author instance in local/staging environment, you can do below steps to test the request.

 

Go to http://localhost:4502/system/console/configMgr

Search for Apache Sling Referrer Filter

Check "Allow Empty"

Remove POST from Filter Methods

 
 

image.png

 

For Production environment, leave the default settings and test via dispatcher.

Please refer to this blog for more details How to make a simple HTTP POST request to AEM with a HTTP Rest Client, Postman - Sourced Code

 
 
kunal23
Correct answer by
Level 10
Level 10

Don't do any changes to white list the host or allow anonymous requests. It is not a recommended option and is not best security practice. You can solve your problem by including CSRF framework clientlib on the page where you have created your form. ClientLib category is -  granite.csrf.standalone

More details - https://helpx.adobe.com/experience-manager/6-2/sites/developing/using/csrf-protection.html

View solution in original post

cecheta
Level 2
Level 2

Thank you for the replies,

@vanegi@BrianKasingli Adding the path to the list of URLs that do not require authentication certainly worked, however it feels like a bit of a workaround. Is there no other way? What has changed in v6.4.8.1? Also I am not sure how I would add a request header from an HTML form.

@ChitraMadan I don't think this is related to the Apache Sling Referrer Filter, the host that makes the POST request has already been added to the Allowed Hosts. I also tried ticking Allow Empty and removing POST from the filter methods but still got the 403.

@kunal23 The granite.csrf.standalone clientlib has already been included on the page, but not inside the iframe. However, I am not sure this issue is related to the CSRF protection, as the servlet path has already been included in the Excluded Paths section of the Adobe Granite CSRF Filter config. I also tried removing POST from the filter methods but still got the 403.

 

Your help would be much appreciated, thank you.

cecheta
Level 2
Level 2

This works for testing, but not for a long term solution. We need to use this form to make the post request within the iframe itself in AEM. Adding the path to the list of URLs that do not require authentication seems like the best option for now