What’s new in HiveMQ Edge 2025.17

HiveMQ Edge now offers enterprise-grade authentication for its web application interface and API, utilizing LDAP. This enhancement allows businesses to centralize user management now for both HiveMQ Edge and the Enterprise Broker through their existing LDAP infrastructure.

Additionally the Workspace has been improved with basic filtering and search capabilities, enabling users to more efficiently locate devices and tags within large topologies.

LDAP Authentication

How it works

LDAP Authentication is configured by adding the ldap entry to the config.xml like this:

    <ldap>
   <servers>
       <ldap-server>
           <host>ldap1.example.com</host>
           <port>636</port>
       </ldap-server>
       <ldap-server>
           <host>ldap2.example.com</host>
           <port>636</port>
       </ldap-server>
       <ldap-server>
           <host>ldap3.example.com</host>
           <port>636</port>
       </ldap-server>
   </servers>
   <tls-mode>LDAPS</tls-mode>
   <max-connections>5</max-connections>
   <simple-bind>
       <rdns>cn=admin</rdns>
       <userPassword>secret</userPassword>
   </simple-bind>
   <uid-attribute>uid</uid-attribute>
   <rdns>ou=people,dc=example,dc=org</rdns>
</ldap>
  

This example will activate LDAP and uses the following features:

• Use three servers in a round robin fashion to improve reliability.
• Activate LDAPS for a TLS secured LDAP connection.
• Have 5 connections in the connection pool for quick responses.
• Use the the user admin with the password "secret" to access LDAP.
• Use the RDNS "ou=people,dc=example,dc=org".

How it helps

HiveMQ Edge now supports LDAP for central user and access control, mirroring the capabilities of HiveMQ Enterprise Broker. This ensures consistent security compliance and password policy enforcement across the entire HiveMQ data streaming solution. This enhancement is especially beneficial for businesses that need to meet ISO and SOC compliance standards for their IT infrastructure, which often require auditing of user actions.

Improvements

🚀 Improvements

• The workspace now has a toolbar for searching or filtering elements in the topology graph.

Deprecation Notice

HiveMQ Edge was migrated to JDK v21 in version 2025.16, HiveMQ Edge will need to be run in the Java run time environment for v21 or higher.

JDK v21 provides many enhancements and improvements to the efficiency and performance of HiveMQ Edge, and enables future data operations capabilities to be brought to the product.

Should you need to run HiveMQ Edge on a 32bit Architecture, or are already running Edge on a 32bit architecture then you should not use any version after 2025.15.

Get Started Today

Use the download link Get HiveMQ Edge 2025.17, or find us on GitHub and Docker:

Get started by running

    docker run --name hivemq-edge --pull=always -d -p 1883:1883 -p 8080:8080 hivemq/hivemq-edge
  

Or clone our repository

    git clone git@github.com:hivemq/hivemq-edge.git
  

You may also try out our Helm Chart

    helm repo add hivemq https://hivemq.github.io/helm-charts && helm repo update