Red Hat AMQ 6
As of February 2025, Red Hat is no longer supporting Red Hat AMQ 6. If you are using AMQ 6, please upgrade: Migrating to AMQ 7.Ce contenu n'est pas disponible dans la langue sélectionnée.
7.2. Secure Transport Protocols
Overview Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
Red Hat AMQ provides a common framework for adding SSL/TLS security to its transport protocols. All of the transport protocols discussed here are secured using the JSSE framework and most of their configuration settings are shared.
Transport protocols Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
Table 7.1, “Secure Transport Protocols” shows the transport protocols that can be secured using SSL/TLS.
URL | Description |
---|---|
ssl://Host:Port | Endpoint URL for Openwire over TCP/IP, where the socket layer is secured using SSL or TLS. |
https://Host:Port | Endpoint URL for Openwire over HTTP, where the socket layer is secured using SSL or TLS. |
stomp+ssl://Host:Port | Endpoint URL for Stomp over TCP/IP, where the socket layer is secured using SSL or TLS. |
mqtt+nio+ssl://Host:Port | Endpoint URL for MQTT over Java NIO, where the socket layer is secured using SSL or TLS. |
Verify Host Name Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
Disabled by default, you can enable the capability of verifying the host name on the transport configuration by using a URL parameter as follows:
ssl://localhost:61616?transport.verifyHostName=true
ssl://localhost:61616?transport.verifyHostName=true
To enable on the client side, use the following:
ssl://localhost:61616?socket.verifyHostName=true
ssl://localhost:61616?socket.verifyHostName=true
Important
It is especially important to
enable
this option to prevent against man-in-the-middle attacks, particularly in locked down systems.