The HiveMQ Enterprise Security Extension (ESE) expands the role, user, and permission-management capabilities of HiveMQ’s Enterprise and Professional editions.
Version: Bundles with HiveMQ
Watch this 3-minute overview of the HiveMQ Enterprise Security Extension to learn how to implement advanced security functionality with HiveMQ.
The HiveMQ Enterprise Security Extension (ESE) expands the role, user, and permission-management capabilities of HiveMQ Enterprise and Professional editions. ESE allows you to use different sources of external authentication and authorization data to authenticate and authorize MQTT clients. In the ESE, you define realms to partition your server into protected areas that can each have their own authentication and/or authorization scheme.
Full support for authentication and authorization via SQL databases.
Full support for authentication and authorization via files.
Full support for OAuth 2.0 authentication for MQTT listeners via JSON Web Tokens.
Configurable client certificate revocation check for MQTT and WebSocket listeners.
Dynamic permission placeholders to individualize topic permissions on a per-client basis.
Ability to implement sophisticated custom logic for authentication over LDAP (Lightweight Directory Access Protocol).
Detailed access log to help you monitor data and keep track of potential security breaches.
HiveMQ is designed from the ground up with maximum security in mind. For mission-critical IoT and M2M scenarios, secure end-to-end encrypted communication and advanced authentication and authorization features are essential. HiveMQ gives you the flexibility to enable the specific security features that your individual use case requires.
HiveMQ extensions are plugins that provide seamless integration with streaming services, databases, data warehouses, and security services. There is a Custom SDK to build tailored extensions for specific integration needs.
Extensions usage scales along with the rest of the cluster and each enterprise extension is designed and tested for use in a cluster.
Extensions run on each cluster node, so if a node exits the cluster the extension will be present on the replacement node.
No separate nodes to manage. Easily manage cluster-wide configuration in a Kubernetes cluster with the HiveMQ Operator.