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 support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

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 support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

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 support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

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 support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

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. Address Federation 16 Highlights: Broker through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

Ability to delete queues and addresses when broker.xml changes. Client authentication via Kerberos TLS Cipher Suites (RFC 2712). 2.1.0 Versions 16 Full release notes. Highlights: Broker plugin support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

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 support. Support through openssl but not through the JDK provider. See https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations for more information's. sniHost When used on an acceptor the sniHost is a with their own certificate. In this scenario, authentication is actually performed during the SSL/TLS handshake, not directly by the JAAS certificate authentication plug-in. The role of the plug-in is

can then connect to ws://:1883 using a Web Socket to send and receive MQTT messages. SSL/TLS is also available, e.g.: tcp://host:8883?protocols=MQTT;sslEn default behavior. For additional details about please refer to section 3.1 of RFC 2818 "HTTP over TLS". 2. Due to ARTEMIS-3117 SSL keystore and truststores are no longer reloaded automatically. Previously 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. 15.40.2. Highlights • Broker plugin support

can then connect to ws://:1883 using a Web Socket to send and receive MQTT messages. SSL/TLS is also available, e.g.: tcp://host:8883?protocols=MQTT;sslEn default behavior. For additional details about please refer to section 3.1 of RFC 2818 "HTTP over TLS". 2. Due to ARTEMIS-3117 SSL keystore and truststores are no longer reloaded automatically. Previously 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. 15.37.2. Highlights • Broker plugin support

can then connect to ws://:1883 using a Web Socket to send and receive MQTT messages. SSL/TLS is also available, e.g.: tcp://host:8883?protocols=MQTT;sslEn default behavior. For additional details about please refer to section 3.1 of RFC 2818 "HTTP over TLS". 2. Due to ARTEMIS-3117 SSL keystore and truststores are no longer reloaded automatically. Previously 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. 15.38.2. Highlights • Broker plugin support