Received request for invokeOp with invalid or missing CSRFToken token. This might indicate that someone is trying CSRF attack on your server.

Solution Verified - Updated -

Issue

Identical JMX console configuration that works on EAP5.1.2 does not work for EAP5.2.0.

When trying to invoke a bean (any) we get in the logfile:

WARN [org.jboss.jmx.adaptor.html.HtmlAdaptorServlet] (http-10.1.1.1-4101-2) Received request for invokeOp with invalid or missing CSRFToken token. This might indicate that someone is trying CSRF attack on your server.

Environment

JBoss Enterprise Application Platform (EAP) 5.2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.