mqtt over websocket: no TLS peer verification

[dambsst]

Describe the bug

According to the documentation, TLS peer verification should be possible but the plugin doesn't recognize the two configuration parameters related to it:

• web_mqtt.ssl.verify
• web_mqtt.ssl.fail_if_no_peer_cert

Reproduction steps

1. Deploy and configure the plugin with TLS as described here https://www.rabbitmq.com/docs/web-mqtt
2. Add two additionnal seetings in the *.conf file:
   web_mqtt.ssl.verify = verify_peer
   web_mqtt.ssl.fail_if_no_peer_cert = true
3. Start the server, it fails during boot.
   ...

Expected behavior

The server should not fail during boot
AND
TLS peer verification should be effective when connecting via wss://
OR
The documentation should be updated to inform that TLS peer verification is not possible with wss://

Additional context

No response

[michaelklishin]

According to the documentation, TLS peer verification should be possible

@dambsst the MQTT-over-WebScoets plugin does support everything in its doc guide.

Neither web_mqtt.ssl.verify nor web_mqtt.ssl.fail_if_no_peer_cert are used in the guide.

Adding them in theory should be a matter of propagating a few more options. You are welcome to look into it, this is open source software after all. This rabbitmq.conf schema part is where the TLS-related keys belong.

[michaelklishin]

The last time that set of settings was updated was over seven years ago in 03709f9.

I guess very few MQTT-over-WebSockets (and STOMP-over-WebSockets) users use peer verification of client connections.