ENTMQBR-428 - Implement SASL external

AMQ Broker can now validate AMQP connections by using the identity of the connection’s SSL certificate rather than using traditional credentials such as a username and password. This benefits deployments where secure access is managed through SSL certificates.

ENTMQBR-893 - Masking of password does not work with login.config

You can now mask passwords in the JAAS configuration file login.config. Previously, password masking was not supported for login.config, which meant that the passwords in the file were stored in plain text.

ENTMQBR-908 - Support masked passwords in bootstrap.xml

You can now mask passwords in the broker.xml configuration file. Previously, password masking was not supported for broker.xml, which meant that the passwords in the file were stored in plain text.

ENTMQBR-935 - Should have Ability to split broker.xml into multiple files and import into broker.xml

AMQ Broker now supports XML inclusions in the broker.xml configuration file, which enables you to break broker.xml into separate files. For example, if you have multiple brokers that share the same set of addresses and address settings, you can define the addresses in a separate file, and then include that file in each broker’s broker.xml configuration file.

ENTMQBR-1056 - Add Support for DB2 v11.latest

The 7.2 version of AMQ Broker adds support for the database DB2, version 11.

ENTMQBR-1063 - Improve DB2 compatibility

AMQ Broker now supports IBM DB2 versions 10.5 and 11.1 for message storage. The following enhancements have been made:

ENTMQBR-1271 - Allow custom etc and data directories to be used

AMQ Broker 7.2 provides greater flexibility in storing a broker instance’s configuration files and data. Previously, a broker instance’s configuration files and data could only be stored in the etc/ and data/ directories within the broker instance’s directory. Now, you can store these files in any custom directory, including locations outside of the broker instance’s directory.

ENTMQBR-1282 - Support for exclusive consumers

AMQ Broker now supports exclusive queues. An exclusive queue routes messages to a single consumer even if multiple consumers are present. In addition, the consumer that receives the messages will receive them with guaranteed message ordering so that they can be consumed in the same order in which they were produced.

ENTMQBR-1308 - Create an ActiveMQServerPlugin for logging various broker events

Starting in AMQ Broker 7.2, logging has been improved through a new LoggingActiveMQServerPlugin. By using this plugin, you can configure highly-informative logging about many different types of events that would otherwise only be available through debug logs.

ENTMQBR-1367 - Support SSL Certificate Revocation List

Starting in AMQ Broker 7.2, you can now specify an SSL certificate revocation list on an acceptor’s URL. If you are using SSL for client communication, this means that you can specify a list of certificates that have been revoked by the issuing certificate authority (CA) before their scheduled expiration date and should no longer be trusted.

ENTMQBR-1385 - Add support for virtual topic consumers

AMQ Broker now supports migrating existing OpenWire clients that use virtual topic subscriptions (an ActiveMQ 5.x-only feature) without requiring any changes to the client. This functionality maps the virtual topic concept to an Artemis fully qualified queue name (FQQN). By using a FQQN, you can create and access a standard Artemis topic subscriber queue.

ENTMQBR-1403 - Support referrals in LDAP login module

AMQ Broker now supports LDAP referrals. If you use LDAP referrals in your LDAP infrastructure, you can now configure the broker to use these referrals to authenticate and authorize users. You can use the broker’s JAAS LDAP login module to control how the broker handles LDAP referrals.