Hawtio and its plugins can configure their behaviours through System properties.
The following table lists the configuration properties for the Hawtio core system and various plugins.
|For the configuration properties related to security and authentication, refer to Security.
With this property set to
Whether local address probing for proxy allowlist is enabled or not upon startup. Set this property to
Comma-separated allowlist for target hosts that Connect plugin can connect to via
The scheme of the redirect URL to login page when authentication is required.
The maximum time interval, in seconds, that the servlet container will keep this session open between client accesses. If this option is not configured, then Hawtio uses the default session timeout of the servlet container.
For Quarkus, all those properties are configurable in
application.yaml with the
quarkus.hawtio. prefix. For example:
quarkus.hawtio.disableProxy = true
The Jolokia agent is deployed automatically with
io.hawt.web.JolokiaConfiguredAgentServlet that extends Jolokia native
org.jolokia.http.AgentServlet class, defined in
If you want to customize the Jolokia Servlet with the configuration parameters that are defined in the Jolokia documentation, you can pass them as System properties prefixed with
jolokia.. For example:
jolokia.policyLocation = file:///opt/hawtio/my-jolokia-access.xml
For some runtimes that support Hawtio RBAC (role-based access control) , Hawtio provides a custom Jolokia restrictor implementation that provides an additional layer of protection over JMX operations based on the ACL (access control list) policy.
|You cannot use Hawtio RBAC with Quarkus and Spring Boot yet. Enabling the RBAC restrictor on those runtimes only imposes additional load without any gains.
To activate the Hawtio RBAC restrictor, configure the Jolokia parameter
restrictorClass via System property to use
io.hawt.web.RBACRestrictor as follows:
jolokia.restrictorClass = io.hawt.system.RBACRestrictor