Skip to main content

TLS in AirNgin

AirNgin supports MQTT over TLS to protect the transport between Device and broker from eavesdropping, tampering, and man-in-the-middle attacks.

Why TLS matters​

TLS provides:

  • encrypted transport;
  • server authentication;
  • integrity protection for the network channel;
  • protection against passive network inspection.

MQTT ports​

1883  MQTT without TLS
8883  MQTT over TLS

Use the same server-issued MQTT username, password, and ClientId with the TLS connection. Your MQTT library must use a secure socket implementation and validate the broker certificate with a trusted CA/certificate chain.

Canonical broker names are:

mqtt.airngin.com
mqtt.airngin.ir

Device clock​

TLS certificate validation depends on a valid local clock. If the Device has no reliable RTC, synchronize its time before opening the TLS connection. See Server time.

TLS and the optional AirNgin AES application layer are independent. You may use TLS, AES, or both according to the product/security policy.