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

AEM 6.4.8.1 (CFP 1) and POST Requests

Avatar

Avatar
Validate 1
Level 1
cecheta
Level 1

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 1
View profile

Avatar
Validate 1
Level 1
cecheta
Level 1

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 1
View profile
cecheta
Level 1

04-08-2020

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
View Entire Topic

Avatar

Avatar
Validate 1
Level 1
cecheta
Level 1

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 1
View profile

Avatar
Validate 1
Level 1
cecheta
Level 1

Likes

2 likes

Total Posts

10 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Give Back
Boost 1
View profile
cecheta
Level 1

05-08-2020

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.