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. Highlights: Broker plugin support. Support can then connect to ws://:1883 using a Web Socket to send and receive MQTT messages. SSL/TLS is also available, e.g.: Web browsers can then connect to wss://:8883 using a Web Socket

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. Highlights: Broker plugin support. Support can then connect to ws://:1883 using a Web Socket to send and receive MQTT messages. SSL/TLS is also available, e.g.: Web browsers can then connect to wss://:8883 using a Web Socket

default behavior. For additional details about please refer to section 3.1 of RFC 2818 "HTTP over TLS". Versions 16 2. Due to ARTEMIS-3117 SSL keystore and truststores are no longer reloaded automatically 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 can then connect to ws://:1883 using a Web Socket to send and receive MQTT messages. SSL/TLS is also available, e.g.: Web browsers can then connect to wss://:8883 using a Web Socket

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. Highlights: Broker plugin support. Versions the client certificates. This is only relevant for a connector if you are using 2-way SSL (i.e. mutual authentication). Although this value is configured on the server, it is downloaded and used by the

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. Versions 23 Highlights: Broker plugin support the client certificates. This is only relevant for a connector if you are using 2-way SSL (i.e. mutual authentication). Although this value is configured on the server, it is downloaded and used by the

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

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.36.2. Highlights • Broker plugin support

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. Highlights: Broker plugin support. Support the client certificates. This is only relevant for a connector if you are using 2-way SSL (i.e. mutual authentication). Although this value is configured on the server, it is downloaded and used by the