WildFly Management Interfaces
Internal
Overview
WildFly core management functionality is exposed via two different management interfaces (the terms management interfaces and management APIs are used interchangeably):
- Native API - used by the Management CLI
- HTTP API - used by the Management CLI and the web-based Management Console.
These two interfaces offer distinct ways to access the same core management system.
Diagram
The Native API Endpoint
The Native API endpoint is the entry point for management clients that rely on the native protocol to integrate with the management layer. It uses an open binary protocol and an RPC-style API based on a small number of Java types to describe and execute management operations. It is used by the CLI management tool, but offers integration capabilities for other clients too.
The HTTP Endpoint
Configuration
Security
Core management authentication is responsible for securing the management interfaces. Core management authentication is built into the core management and it is enabled and configured as a core service by default.
The management APIs relies on the Management Realm for authentication and authorization needs: in order to access the management API functionality, a user need to successfully authenticate against the Management Realm. Note that by default, no roles are required to access the management APIs, authentication is sufficient.
JMX Management Beans
The management API is also exposed as JMX Management Beans. These Management Beans are referred to as core mbeans. Prior to WildFly, the management functionality was primarily JMX based. With WildFly, the core management does not rely on JMX to perform operations, JMX exposed beans are now just an alternative mechanism, in addition to the native and HTTP interfaces.
JMX clients can connect to the JMX Management Beans over the same native management interface.