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

:cq_csrf_token and form container core component

Avatar

Avatar
Give Back 5
Level 3
Julio_Baixauli
Level 3

Likes

22 likes

Total Posts

82 posts

Correct Reply

6 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 25
View profile

Avatar
Give Back 5
Level 3
Julio_Baixauli
Level 3

Likes

22 likes

Total Posts

82 posts

Correct Reply

6 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 25
View profile
Julio_Baixauli
Level 3

17-06-2019

Hi masters!

I'm trying to use the 'Form Container', from core components (core/wcm/components/form/container/v2/container), to send emails, configuring the 'Action Type' to 'Mail'.

But when the form is sent to the thank you page, a 403 message is shown, and I can see this in the error.log:

17.06.2019 10:30:23.629 *INFO* [0:0:0:0:0:0:0:1 [1560760223623] POST /content/hesperiaweb/language-masters/es/contacto.html HTTP/1.1] com.adobe.granite.csrf.impl.CSRFFilter isValidRequest: empty CSRF token - rejecting

17.06.2019 10:30:23.629 *INFO* [0:0:0:0:0:0:0:1 [1560760223623] POST /content/hesperiaweb/language-masters/es/contacto.html HTTP/1.1] com.adobe.granite.csrf.impl.CSRFFilter doFilter: the provided CSRF token is invalid

I've done this in previous versions of AEM with the former 'foundation/components/form/start' component, and this component added the :cq_csrf_token field to the request. But it seems the new core component doesn't, or I miss something...

Could you help me?

Kind regards,

Replies

Avatar

Avatar
Ignite 1
Employee
aemmarc
Employee

Likes

184 likes

Total Posts

243 posts

Correct Reply

92 solutions
Top badges earned
Ignite 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Ignite 1
Employee
aemmarc
Employee

Likes

184 likes

Total Posts

243 posts

Correct Reply

92 solutions
Top badges earned
Ignite 1
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
aemmarc
Employee

17-06-2019

You need to check that the CSRF-Token is passed in the /clientheaders section in Dispatcher.

Avatar

Avatar
Give Back 5
Level 3
Julio_Baixauli
Level 3

Likes

22 likes

Total Posts

82 posts

Correct Reply

6 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 25
View profile

Avatar
Give Back 5
Level 3
Julio_Baixauli
Level 3

Likes

22 likes

Total Posts

82 posts

Correct Reply

6 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Ignite 1
Validate 25
View profile
Julio_Baixauli
Level 3

17-06-2019

Hi aem_marc.

I'm using only an AEM 6.5 author instance (no publish instance, no dispatcher). With admin user!

Thank you anyway!

Kind regards,

Avatar

Avatar
Validate 1
Level 2
victor_toledo_3
Level 2

Likes

14 likes

Total Posts

39 posts

Correct Reply

4 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile

Avatar
Validate 1
Level 2
victor_toledo_3
Level 2

Likes

14 likes

Total Posts

39 posts

Correct Reply

4 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back
View profile
victor_toledo_3
Level 2

08-08-2019

Hi Julio, have you solved this problem? I face a similar problem after trying to configure an external URL as a thank you page.