---
schema_version: "1"
id: 1891d112247e739e1ac76c3893325f47e84166106c77c7155716bd7d68c1d953
title: MQTT Connector FAQ
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mqtt3-connector/latest/mqtt3-connector-faq.md
canonical_url: https://docs.mulesoft.com/mqtt3-connector/latest/mqtt3-connector-faq
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 35eeaaa4b2fe50f28d45fc5546f868dc109ad64564a847677d4db9af66b9911a
description: MuleSoft Documentation Site
release: "1.1"
latest: true
---
---
product: MQTT Connector
version: 1.1
is-latest-version: true
---

# MQTT Connector FAQ

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

MQTT Connector frequently asked questions (FAQ) are:

## Does MQTT Connector use an object store for the Enable File Persistence feature?

The **Enable file persistence** feature is available only on the on-premises installation and uses a
file for persistent messages. Note that an object store enables persistent storage for CloudHub
applications. Refer to the [object store](https://docs.mulesoft.com/object-store/) documentation for details.

## Is MQTT Connector supported on CloudHub and Cluster environments?

Yes, MQTT Connector is supported on CloudHub and on cluster environments.

## Is MQTT Connector cluster-aware?

MQTT Connector is cluster-aware. MQTT brokers usually implement a client takeover mechanism that
closes an old connection if a new connection request with the same client ID as the existing (old)
connection is received and then accepts the new connection. The client takeover mechanism can become
a problem if you want to deploy an application in a cluster, and still provide an explicit client ID
that identifies the client. MQTT Connector provides client ID generators that help you set a static
client ID, set a client ID with a dynamic component to adjust to different deployment scenarios, or
define your custom client ID generator.

For further information, refer to the
[set a Client ID with MQTT Connector](https://docs.mulesoft.com/mqtt3-connector/latest/mqtt3-connector-client-id) documentation.

## What are the authentication types supported?

MQTT Connector authentication supports user and password, and certificate-based authentication (TLS
or WSS). Refer to the
[configure credentials for authentication](https://docs.mulesoft.com/mqtt3-connector/latest/mqtt3-connector-studio-configuration#configure-authentication)
documentation.

## Does MQTT Connector trace connection and operation executions?

Refer to the [Troubleshooting MQTT Connector](https://docs.mulesoft.com/mqtt3-connector/latest/mqtt3-connector-troubleshooting) documentation to
learn how to enable verbose logging in DEBUG mode for the connector, for Eclipse Paho driver and the
Mosquitto broker.

## What is the server-side configuration required for MQTT Connector to work?

MQTT Connector works with any MQTT version 3.x compliant server also known as MQTT broker. To
configure the server, refer to your MQTT broker’s documentation, for example, the
[Eclipse Mosquitto](https://mosquitto.org/documentation) broker documentation.

## Does MQTT Connector use a 3rd party library to connect with the external system?

MQTT Connector uses Eclipse Mosquitto libraries. The ArtifactID is `org.eclipse.paho.client.mqttv3`.

## Is there any documentation or release notes for the Eclipse Mosquitto external library?

To get release notes for Eclipse Mosquitto library, refer to the
[Eclipse public repository](https://github.com/eclipse-paho/paho.mqtt.java/releases).

## Are there any permission, roles, or additional configuration required on the broker side to connect with our credentials using MQTT Connector?

No, there aren’t any additional permissions or configuration requirements to connect to MQTT version
3.x compliant MQTT brokers. On the MQTT broker side, you do need to configure the listeners
properly.

## See Also

- [Salesforce Help](https://help.salesforce.com)