I’m encountering an issue with X509 certificate authentication that persists despite completing all necessary steps. Following the guide available at Cumulocity Documentation for generating a self-signed certificate using OpenSSL on a Windows machine, I’ve successfully completed the process up to the point where the certificate is enabled.
Here are the steps I’ve taken:
- Generated a self-signed certificate using OpenSSL on my Windows machine.
- Created and uploaded the Certificate Authority (CA).
- Performed Proof of Possession (PoP) to validate the certificate.
- Enabled the certificate according to the documentation.
Following the successful generation and setup of a self-signed certificate as described in the Cumulocity documentation, I attempted to authenticate using Postman. Specifically, I tried to use deviceCert.pem and devicekey.pem files, including the passphrase required for authentication. but get this error below:
To provide a clearer picture of the issue and aid in troubleshooting, I’ve prepared several snapshots detailing my configuration process.
-
Successful Certificate Upload to Cumulocity: This snapshot demonstrates the successful upload of the certificate to Cumulocity, confirming that the certificate authority has been set up correctly.
-
Certificate Configuration in Postman: The second snapshot illustrates how the certificate (
deviceCert.pem) and key (devicekey.pem) are configured within Postman, including the passphrase required for authentication. -
MQTT Connect Call and Failure Response: The third snapshot captures the MQTT connect call made from Postman and the failure response received, highlighting the point of failure in the authentication process.
Could anyone offer insights or solutions based on this configuration? Are there specific adjustments or settings within Postman that might resolve the authentication issue? or is there something else I am doing wrong?
