Intended use case for granite.jquery's csrf.js

[Joel_Triemstra1]

We’re running into some Javascript errors in Internet Explorer that we’ve tracked down to /etc/clientlibs/granite/jquery/granite/csrf/source/csrf.js

Specifically, the line handleForm(result.contentWindow.document)is a problem when an iframe contains content from a different domain.

I suspect I can set up an overlay to work around this, but wanted to get some input as far as what the intended use case for this behavior is, or if there are specific components in AEM that are relying on it, so we can be prepared for any future problems that may arise.

Thanks

[smacdonald2008]

FRom reading the code - looks like this is helping against:

https://en.wikipedia.org/wiki/Cross-site_request_forgery

Also- i sent this question other Adobe ppl so they can help with this question. 

[Opkar_Gill · Accepted solution]

Hi,

some details here [1][2], as Scott mentioned it is part of the security framework in AEM and as such should not be modified. If you have specific issues, I'd suggest raising a support ticket.

Regards,

Opkar

[1] https://docs.adobe.com/docs/en/aem/6-1/develop/security.html

[2] https://docs.adobe.com/docs/en/aem/6-1/develop/security/csrf-protection.html

[akkul_reddy]

Hi,

We are using google Recaptcha  as a component on our forms.It is not able to get the options which we have to select to solve the recaptcha, it is continuously loading. We are facing this problem in IE11,after debugging came to know that it is failing handleForm(result.contentWindow.document);(/etc/clientlibs/granite/jquery/granite/csrf/source/csrf.js)  in this location.Please suggest me how we can resolve this issue.

Thanking you.