MQ Light clients, or web browsers, exchange data with the MQ Light server by connecting over a network. When data is sent over a network in this way it can be vulnerable to interception or modification by other systems on the network.

The following unwanted scenarios can occur when an unknown user can intercept and/or modify the data sent over the network:

  • Message data exchanged between the MQ Light client and server can be read, and potentially the message payload can be changed to contain different data.
  • Username/Password values that the client uses to authenticate with the MQ Light server can be captured, and used to impersonate the client.
  • The operations of the client connected to an MQ Light server can be disrupted, including preventing the client from being able to maintain a connection to the MQ Light server.

MQ Light implements the SSL (Secure Socket Layer) and TLS (Transport Layer Security) protocols to protect the privacy and integrity of the data exchanged between the MQ Light client and server, as well as the data exchanged between web browsers and the MQ Light server. In environments where you do not have complete control over the systems connected to the network as the MQ Light server, using SSL will protect communication to the server.

For more information on SSL/TLS security, see Securing MQ Light.


The example below shows how a Node.js application would connect using SSL security, by specifying the AMQPS protocol on the service property:

var mqlight = require('mqlight');
var opts = {
  // This URL would start 'amqp://' if the server was not using SSL...
  service: 'amqps://localhost/'
var client =  mqlight.createClient(opts);

For more information about using the service property with the Node.js API, see MQ Light Node.js API

Join The Discussion

Your email address will not be published.