Secure way to post data to Cumulocity using webMethods.io http connector?

Product/components used and version/fix level:

WebMethods.io, version- [11.0.3.0]

Detailed explanation of the problem:

I am using webMethods.io http connector to post measurements to Cumulocity platform. Is there any secure way to post data to Cumulocity as there is no https connector available ?
Can we convert http connector to https connection to ensure the data is encrypted and remain secured?

Error messages / full error message screenshot / log file:

Question related to a free trial, or to a production (customer) instance?

Production.

1 Like

If I understand correctly, you’re using the “HTTP Connector”, not the “Cumulocity IoT” Connector that Stefan mentioned, correct? Although the name does not suggest, the “HTTP Connector” also supports https endpoints.

Anyway we’d recommend to use the “Cumulocity IoT” connector which gives you a lot of features to work with your Cumulocity tenant. If you need any support using it, let us know!

2 Likes

Hi @Michael_Voigt2

Using HTTP connector since the measurements are dynamic and can differ from device to device.
I would like to know how secure is HTTP connector ?

Thanks in advance,
Nithya

To be honest I dont know how secure the HTTP Connector is since I never used it or developed it. But using https should give you some security after all.

3 Likes

Just to reiterate, when you connect to a Cumulocity IoT Cloud instance, you can only use HTTPS so all traffic is always encrypted.

3 Likes

Further to our discussion above, my internal team has raised concern that the data which is in transit, webMethods.io-> c8y is not secure. As the port I am using is HTTP from webMethods.io to send the data to c8y. Hence please confirm the data that is transferred is encrypted or not.

Please refer to the attached image for the connector we are using and the url which is used to post the data.

Your early response is appreciated.

Just repeating what @Harald_Meyer already said in the previous post. You are using the https://* address (as per your own screenshot), so it is using encrypted traffic.

3 Likes