JNDIReferenceFactory and JNDIStorable. Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" support to authenticate SSL-based and non-SSL-based clients differently. 1.3.0 Full release password --ssl-trust The trust store path in case of client authentication --ssl-trust-password The trust store password

JNDIReferenceFactory and JNDIStorable. Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" support to authenticate SSL-based and non-SSL-based clients differently. 1.3.0 Full release password --ssl-trust The trust store path in case of client authentication --ssl-trust-password The trust store password

JNDIReferenceFactory and JNDIStorable. Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" support to authenticate SSL-based and non-SSL-based clients differently. 1.3.0 Full release password --ssl-trust The trust store path in case of client authentication Using the Server 29 --ssl-trust-password The trust

password --ssl-trust The trust store path in case of client authentication --ssl-trust-password The trust store password --use-client-auth If the embedded server requires client authentication --user The username (Default: input) --verbose Adds more Artemis to use JAAS for security. Apache ActiveMQ Artemis can leverage JAAS to delegate user authentication and authorization to existing security infrastructure. JMS Auto Closable Examples 55 The

JNDIReferenceFactory and JNDIStorable. Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Full release notes. Highlights: Broker plugin permission for clients who only wish to look at messages. Option to populate JMSXUserID. "Dual authentication" support to authenticate SSL-based and non-SSL-based clients differently. 1.3.0 Full release password --ssl-trust The trust store path in case of client authentication --ssl-trust-password The trust store password

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.15. Enhanced Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 43. Authentication & Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15. Enhanced Authentication MQTT 5 introduced enhanced authentication which extends the existing name & password authentication to include challenge / response style authentication. However, there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.15. Enhanced Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 42. Authentication & Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15. Enhanced Authentication MQTT 5 introduced enhanced authentication which extends the existing name & password authentication to include challenge / response style authentication. However, there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.15. Enhanced Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 42. Authentication & Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15. Enhanced Authentication MQTT 5 introduced enhanced authentication which extends the existing name & password authentication to include challenge / response style authentication. However, there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.15. Enhanced Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 42. Authentication & Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15. Enhanced Authentication MQTT 5 introduced enhanced authentication which extends the existing name & password authentication to include challenge / response style authentication. However, there

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 8.15. Enhanced Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 43. Authentication & Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15. Enhanced Authentication MQTT 5 introduced enhanced authentication which extends the existing name & password authentication to include challenge / response style authentication. However, there