Contents
Cirrus Link Resources
Chariot MQTT Server v1 (previous version)
Cirrus Link Modules for Ignition
Contact Us (Sales/Support)
Forum
...
Generate a private key file (serverCA.key) for the Server CA using the command below. You will be required to enter a pass phrase to be associated with the serverCA.key file.
Code Block | ||
---|---|---|
| ||
openssl genrsa -des3 -out ca/server/serverCA.key 2048 |
Generate a Certificate Signing Request (CSR) for the server CA using the command below. This command generates a new CSR named "serverCA.csr’ using the RSA private key "serverCA.key" and you will be required to enter the pass phrase created in the previous step.
Code Block | ||
---|---|---|
| ||
openssl req -new -key ca/server/serverCA.key -out ca/server/serverCA.csr |
Note |
---|
There are a number of fields associated with the creation of the certificate. The required fields are: Country Name (2 letter code) []: State or Province Name (full name) []: Locality Name (eg, city) []: Organization Name (eg, company) []: Organizational Unit Name (eg, section) []: We set this as Server CA Common Name (eg, fully qualified host name) []: We set this as the FQDN of the Chariot server Email Address []: Extra attributes to be sent with the certificate request are: A challenge password []: You will be required to enter the keystore password and this can be found in the <chariot_install_dir>/conf/com.cirruslink.chariot.system configuration file as the "keyStorePassword" parameter. |
Sign the Server CA with the Root CA using the command below. This command will sign the CSR "serverCA.csr" with the Root CA certificate ‘ca.crt’ and RSA private key ‘ca.key’, creating a new X.509 certificate named ‘serverCA.crt’ valid for 3650 days (10 years). A "serverCA.srl" file will also be created containing the signed certificate's unique serial number. You will be required to enter the pass phrase associated with the private key file "ca.key".
Code Block | ||
---|---|---|
| ||
openssl x509 -req -in ca/server/serverCA.csr -CA ca/ca.crt -CAkey ca/ca.key -CAcreateserial -out ca/server/serverCA.crt -days 3650 |
...
Generate a private key file (engineCA.key) for MQTT Engine CA using the command below. You will be required to enter a pass phrase to be associated with the engineCA.key file.
Code Block | ||
---|---|---|
| ||
openssl genrsa -des3 -out ca/engine/engineCA.key 2048 |
Generate a Certificate Signing Request (CSR) for the MQTT Engine CA using the command below. This command generates a new CSR named "engineCA.csr’ using the RSA private key "engineCA.key" and you will be required to enter the pass phrase created in the previous step.
Code Block | ||
---|---|---|
| ||
openssl req -new -key ca/engine/engineCA.key -out ca/engine/engineCA.csr |
Note |
---|
There are a number of fields associated with the creation of the certificate. The required fields are: Country Name (2 letter code) []: State or Province Name (full name) []: Locality Name (eg, city) []: Organization Name (eg, company) []: Organizational Unit Name (eg, section) []: We set this as MQTT Engine CA Common Name (eg, fully qualified host name) []: We set this as the FQDN of the Chariot server Email Address []: Extra attributes to be sent with the certificate request are: A challenge password []:You will be required to enter the keystore password and this can be found in the <chariot_install_dir>/conf/com.cirruslink.chariot.system configuration file as the "keyStorePassword" parameter. |
Sign the MQTT Engine CA with the Root CA using the command below. This command will sign the CSR "Sign the MQTT Engine CA with the Root CA using the command below. This command will sign the CSR "engineCA.csr" with the Root CA certificate ‘ca.crt’ and RSA private key ‘ca.key’, creating a new X.509 certificate named ‘engineCA.crt’ valid for 3650 days (10 years). An "engineCA.srl" file will also be created containing the signed certificate's unique serial number. You will be required to enter the pass phrase associated with the private key file "ca.key".
Code Block | ||
---|---|---|
| ||
openssl x509 -req -in ca/engine/engineCA.csr -CA ca/ca.crt -CAkey ca/ca.key -CAcreateserial -out ca/engine/engineCA.crt -days 3650 |
...
Generate a private key file (transmissionCA.key) for MQTT Transmission CA using the command below. You will be required to enter a pass phrase to be associated with the transmissionCA.key file.
Code Block | ||
---|---|---|
| ||
openssl genrsa -des3 -out ca/transmission/transmissionCA.key 2048 |
Generate a Certificate Signing Request (CSR) for the MQTT Transmission CA using the command below. This command generates a new CSR named "transmissionCA.csr’ using the RSA private key "transmissionCA.key" and you will be required to enter the pass phrase created in the previous step.
Code Block | ||
---|---|---|
| ||
openssl req -new -key ca/transmission/transmissionCA.key -out ca/transmission/transmissionCA.csr |
Note |
---|
There are a number of fields associated with the creation of the certificate. The required fields are: Country Name (2 letter code) []: State or Province Name (full name) []: Locality Name (eg, city) []: Organization Name (eg, company) []: Organizational Unit Name (eg, section) []: We set this as MQTT Transmission CA Common Name (eg, fully qualified host name) []: We set this as the FQDN of the Chariot server Email Address []: Extra attributes to be sent with the certificate request are: A challenge password []:You will be required to enter the keystore password and this can be found in the <chariot_install_dir>/conf/com.cirruslink.chariot.system configuration file as the "keyStorePassword" parameter. |
Sign the MQTT Transmission CA Sign the MQTT Transmission CA with the Root CA using the command below. This command will sign the CSR "transmissionCA.csr" with the Root CA certificate ‘ca.crt’ and RSA private key ‘ca.key’, creating a new X.509 certificate named ‘transmissionCA.crt’ valid for 3650 days (10 years). An "transmissionCA.srl" file will also be created containing the signed certificate's unique serial number. You will be required to enter the pass phrase associated with the private key file "ca.key".
Code Block | ||
---|---|---|
| ||
openssl x509 -req -in ca/transmission/transmissionCA.csr -CA ca/ca.crt -CAkey ca/ca.key -CAcreateserial -out ca/transmission/transmissionCA.crt -days 3650 |
...
Generate private key (server.key) for the Chariot server using the command below.
Note |
---|
openssl genrsa -out certs/server/server.key 2048 |
Generate a Certificate Signing Request (CSR) for the Chariot server using the command below. This command generates a new CSR named "server.csr’ using the RSA private key "server.key".
Code Block | ||
---|---|---|
| ||
openssl req -new -key certs/server/server.key -out certs/server/server.csr |
Note |
---|
There are a number of fields associated with the creation of the certificate. The required fields are: Country Name (2 letter code) []: State or Province Name (full name) []: Locality Name (eg, city) []: Organization Name (eg, company) []: Organizational Unit Name (eg, section) []: We set this as Chariot Common Name (eg, fully qualified host name) []: We set this as the FQDN of the Chariot server Email Address []: Extra attributes to be sent with the certificate request are: A challenge password []:You will be required to enter the keystore password and this can be found in the <chariot_install_dir>/conf/com.cirruslink.chariot.system configuration file as the "keyStorePassword" parameter. |
Sign the Server CSR with the Server CA using the command below. This command will sign the CSR "server.Sign the Server CSR with the Server CA using the command below. This command will sign the CSR "server.csr" with the Server CA certificate ‘serverCA.crt’ and RSA private key ‘serverCA.key’, creating a new X.509 certificate named ‘serverCA.crt’ valid for 3650 days (10 years). You will be required to enter the pass phrase associated with the private key file "serverCA.key".
Code Block | ||
---|---|---|
| ||
openssl x509 -req -in certs/server/server.csr -CA ca/server/serverCA.crt -CAkey ca/server/serverCA.key -CAcreateserial -out certs/server/server.crt -days 365 |
...
Generate private key (engine.key) for MQTT Engine using the command below.
Code Block | ||
---|---|---|
| ||
openssl genrsa -out certs/engine/engine.key 2048 |
Generate a Certificate Signing Request (CSR) for MQTT Engine using the command below. This command generates a new CSR named "engine.csr’ using the RSA private key "engine.key".
Code Block | ||
---|---|---|
| ||
openssl req -new -key certs/engine/engine.key -out certs/engine/engine.csr |
Note |
---|
There are a number of fields associated with the creation of the certificate. The required fields are: Country Name (2 letter code) []: State or Province Name (full name) []: Locality Name (eg, city) []: Organization Name (eg, company) []: Organizational Unit Name (eg, section) []: We set this as MQTT Engine Common Name (eg, fully qualified host name) []: We set this as the FQDN of the Chariot server Email Address []: Extra attributes to be sent with the certificate request are: A challenge password []:You will be required to enter the keystore password and this can be found in the <chariot_install_dir>/conf/com.cirruslink.chariot.system configuration file as the "keyStorePassword" parameter. |
Sign the MQTT Engine Client Sign the MQTT Engine Client CSR with the Engine CA using the command below. This command will sign the CSR "engine.csr" with the Engine CA certificate ‘engineCA.crt’ and RSA private key ‘engineCA.key’, creating a new X.509 certificate named ‘engineCA.crt’ valid for 3650 days (10 years). You will be required to enter the pass phrase associated with the private key file "engineCA.key".
Code Block | ||
---|---|---|
| ||
openssl x509 -req -in certs/engine/engine.csr -CA ca/engine/engineCA.crt -CAkey ca/engine/engineCA.key -CAcreateserial -out certs/engine/engine.crt -days 365 |
...
Generate private key (transmission.key) for MQTT Transmission using the command below.
Code Block | ||
---|---|---|
| ||
openssl genrsa -out certs/transmission/transmission.key 2048 |
Generate a Certificate Signing Request (CSR) for MQTT Transmission using the command below. This command generates a new CSR named "transmission.csr’ using the RSA private key "transmission.key".
Code Block | ||
---|---|---|
| ||
openssl req -new -key certs/transmission/transmission.key -out certs/transmission/transmission.csr |
Note |
---|
There are a number of fields associated with the creation of the certificate. The required fields are: Country Name (2 letter code) []: State or Province Name (full name) []: Locality Name (eg, city) []: Organization Name (eg, company) []: Organizational Unit Name (eg, section) []: We set this as MQTT Transmission Common Name (eg, fully qualified host name) []: We set this as the FQDN of the Chariot server Email Address []: Extra attributes to be sent with the certificate request are: A challenge password []:You will be required to enter the keystore password and this can be found in the <chariot_install_dir>/conf/com.cirruslink.chariot.system configuration file as the "keyStorePassword" parameter. |
Sign the MQTT Transmission Client CSR with the Transmission CA using the command below. This command will sign the CSR "transmission.Sign the MQTT Transmission Client CSR with the Transmission CA using the command below. This command will sign the CSR "transmission.csr" with the Transmission CA certificate ‘transmissionCA.crt’ and RSA private key ‘transmissionCA.key’, creating a new X.509 certificate named ‘transmissionCA.crt’ valid for 3650 days (10 years). You will be required to enter the pass phrase associated with the private key file "transmissionCA.key".
Code Block | ||
---|---|---|
| ||
openssl x509 -req -in certs/transmission/transmission.csr -CA ca/transmission/transmissionCA.crt -CAkey ca/transmission/transmissionCA.key -CAcreateserial -out certs/transmission/transmission.crt -days 365 |
...
...
By default Chariot comes with an For the Two-Way handshaking to work we need to set the truststore on Chariot. By default Chariot comes with an empty truststore file clientcerts.jks which is located in the <chariot_install_dir>/security folder.
...
Code Block | ||
---|---|---|
| ||
keytool -list -v -keystore clientcerts.jks |
You will see that the truststore contains no entries. Use the following commands to add client side certificates to the truststore using the "trustStorePassword" when prompted:
Code Block | ||
---|---|---|
| ||
keytool -importcert -file engineCA.crt -keystore clientcerts.jks -alias engineca keytool -importcert -file transmissionCA.crt -keystore clientcerts.jks -alias transmissionca |
Once completed, viewing the file will now show two entries.
Tip |
---|
Keytool is part of the standard java distribution and is located in the bin sub-directory of your jdk is installation directory. Chariot will always include a java distribution under the <chariot_install_dir>/lib/runtime |
...