Soracom Beam now supports sending client certificates during the TLS/SSL handshake when sending data to a destination server via HTTPS. This update improves the security of HTTPS by enabling devices to authenticate their identity to the destination server using customer-specified certificates.

While Soracom Beam has supported client certificates for MQTTS connections, it was previously not possible to do the same for HTTPS connections. Instead, client certificates had to be managed directly on a device, increasing the complexity of device implementation and certificate management across large numbers of devices.

Now, client certificates can be specified in Soracom Beam. Devices only need to send data to a Soracom Beam entry point using a lightweight protocol like HTTP or TCP, and in turn Soracom Beam will handle the TLS/SSL handshake using the specified client certificate on behalf of the device. This simplifies certificate management, reduces operational overhead, and allows you to focus more on developing critical features.

The following entry points now support client certificate authentication:

• HTTP to HTTPS Entry Point
• Website Entry Point (*)
• TCP to HTTPS Entry Point
• UDP to HTTPS Entry Point

This feature is also available when using Soracom Beam via the Unified Endpoint.

* Website Entry Point is not supported with Unified Endpoint.

For detailed configuration instructions, please refer to the documentation for each Soracom Beam entry point listed above.

If you have any questions, feel free to contact Soracom Support.