Contents
Cirrus Link Resources
Chariot MQTT Server v1 (previous version)
Cirrus Link Modules for Ignition
Contact Us (Sales/Support)
Forum
Page History
...
When installed on Linux, Windows or deployed via Azure Marketplace, the default User login credentials are:
| Code Block |
|---|
username: admin password: password |
When deployed via AWS Marketplace, the default User login credentials are:
| Code Block |
|---|
username: admin password: EC instance ID for example: i-0049ac1e13e558b70 |
...
- Username
- A unique username for the Chariot User (required).
- Password
- A secure password for the Chariot User that will be used to log into the Chariot Web UI (required).
- Email
- An email address associated with the Chariot User (optional).
- First Name
- A first name associated with the Chariot User (optional).
- Last Name
- A last name associated with the Chariot User (optional).
- Roles
- A list of Chariot Roles associated with the Chariot User.
| Note |
|---|
| By default, a User with the Username admin and Password password will be created |
The "Add" button in the bottom right of the form can be clicked to create the User.
...
- Username
- A unique username that an MQTT client will use when connecting.
- Password
- A secure password that an MQTT client will use when connecting.
- Publish Topics
- A list of MQTT topic filters that the client is allowed to publish on (wildcards may be used).
- Subscribe Topics
- A list of MQTT topic filters that the client is allowed to subscribe on (wildcards may be used).
| Note |
|---|
By default, two default MQTT Credentials are created: Username admin Password changeme Username anonymous Password changeme |
The "Add" button in the bottom right of the form can be clicked to create the Credential.
...
- Name
- A unique name for the bridge connection.
- Enabled
- Sets the enable state of the bridge connection.
- Username
- Optional username for connecting to the server.
- Address
- The server address.
- Port
- The server port.
- Use TLS
- Whether the bridge connection will be using SSL/TLS.
Note By default Chariot comes with an empty truststore file clientcerts.jks which overrides the JVM cacerts truststore. If TLS is enabled, the following lines will need to be removed from the <Chariot_install_directory>/conf/com.cirruslink.chariot.system config file:
- trustStoreFile="security/clientcerts.jks"
- trustStorePassword="secretpassword"
If the signer of the SSL/TLS cert installed on the remote MQTT Server is an external, commercial CA (e.g., DigiCert) the bridge client should successfully connect over TLS once you update the config file and restart Chariot.
If the signer of the SSL/TLS cert installed on the remote MQTT Server is an internal, non-commercial, you will need to add your Root CA cert to the JVMs cacerts trust store and restart Chariot.
...
Overview
Content Tools