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

Previously, Soracom Beam allowed the use of client certificates for MQTTS communication, but it was not possible to use client certificates for HTTPS communication. As a result, when sending data to servers that required client certificates, devices had to manage the certificates themselves. This led to increased complexity in device implementation, particularly when deploying a large number of devices, as it required significant effort to update and manage certificates.

With this new feature, client certificates can now be specified in Soracom Beam. This means that devices only need to send data to Soracom Beam's entry point using simple protocols like HTTP or TCP, even when transmitting data to destination servers that require client certificates. 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.

* The Website Entry Point does not support Unified Endpoint.

For detailed configuration instructions, please refer to the documentation for each entry point.

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

Soracom remains committed to improving its services based on your needs and feedback. Stay tuned for more updates!