Hi @kbitra1998 were you able to get CSRF token in the publish instance? because I have the same scenario now and not sure if I can use CSRF in publish or go with any other approach. Update: http://localhost:4503/libs/granite/csrf/token.json doesn't create a token when logged out, so this cannot be u...
If this is a CSRF filter issue then I think the best way to handle this is by following Adobe's recommendation - by generating a CSRF token while submitting a POST request (for authenticated users). Please check the logs as @Uppari_Ramesh mentioned & if you see CSRF related error messages then pleas...
Hi @Yonit & @lokesh426 It should be the clientheaders file located under the projects dispatcher module dispatcher/src/conf.dispatcher.d/clientheaders/default_clientheaders.any Please check if this file has "CSRF-Token" included in the list. Hope this helps.
Hi @Rajalakshmi There is one way to do this, expose ${currentPage.path} in the component's sightly and ask FE to send it as part of request body (dont do as query param). So once you have it in the servlet you can use it accordingly. Hope this helps.
Can you try once by stopping the aem-precompileompiled-scripts bundle? If it works then I think this needs to be reported to Adobe. I'm also facing a similar issue where I'm trying to load a 3rd party script inside the <head> after overriding head.html from v3/page but it doesn't work because the ht...
Hi @arunpatidar , That solves the issue for me as well when I was trying to load a 3rd party script in the <head> section of the page, but how do we achieve this is in Prod? since you said we should not stop this bundle in Prod.I had overriden the head.html under my apps package (/apps/project/compo...
Hi, has anyone passed data from Process to Container step in the workflow? I'm a bit struggling to achieve the same. Tried using the workItem object and adding to its MetaDataMap() but doesn't seem to work for me. Process step: public void execute (WorkItem workItem, WorkflowSession workflowSession...