Closed kavinManickam closed 1 year ago
@kavinManickam Can you explain this a bit more? Are you running this on. AEM Author or on AEM Publish?
The idea with this tool is would setup agents that can flush dispatcher from AEM Author, not running the UI on Publish and flushing from there.
@davidjgonzalez We are currently installing this on both instances but dispatcher flush is mainly used in publish. The idea here is to setup flush UI in publish and configure "Agents on publish" to flush the dispatcher. This was working with previous ACS versions up to 5.7.0. The main reason to use it in publish is so that the flush paths and flushing method could not be edited.
@kavinManickam can you see if updating your configuration.html
to the following works?
I assume youre logged into AEM Publish to execute this right? And you've permissioned the pages so others can flush your cache?
Hi @davidjgonzalez , I tried updating my configuration.html as mentioned above and it is working as expected. I logged in Publish to execute this as well as in author mode. Other members were also able to flush the dispatcher in Publisher
Thanks for confirming @kavinManickam ! well get this merged and released!
Required Information
Expected Behavior
On configuring Agents on author for author instance and agents on publish for publish instance should be able to flush dispatcher successfully
Actual Behavior
In publish instance on dispatcher flush page load null pointer exception is observed in logs.
This in return is failing to create CSRF token resulting in 403 error.
Steps to Reproduce
Starting from vanilla instance,
Links
https://archive.apache.org/dist/httpd/