mTLS client certificates are widely used to authenticate devices when they connect to remote servers.

In embedded systems, certificate support depends not only on the TLS standard but also on the hardware resources, TLS implementation, firmware, and available cryptographic functions of each device.

For this reason, mTLS client certificates should be considered at device level rather than assuming identical support across an entire product family.

For TCW242, TCW260, TCG120-4 and TCG140-4, a common certificate and server configuration can be used to establish secure mTLS connections.

Here are the mTLS client certificate and server requirements we recommend for these devices.

mTLS client certificates for Teracom devices and an mTLS server

mTLS Client Certificates Depend on the Individual Device

The first important point is that certificate support should be considered at device level.

Different Teracom products use different hardware platforms and TLS implementations. Available memory and processing resources also vary.

TCW242 and TCW260 support the certificate configuration described in this article.

TCG120-4 and TCG140-4 also support this configuration through the TLS functionality of their cellular modules.

Older or more resource-constrained devices may have different capabilities.

For example, TCW122 does not support client certificates because its hardware resources are not sufficient for this functionality.

This is why we do not recommend assuming certificate support based only on the product family.

A Common Configuration for mTLS Client Certificates

For TCW242, TCW260, TCG120-4 and TCG140-4, we recommend using an RSA-2048 client public key.

The client certificate should use PEM encoding. The matching RSA private key should also use PEM encoding and be stored as an unencrypted traditional PKCS#1 private key.

The certificate and private key must form a matching pair.

When client certificate authentication is required, the CA that issued the client certificate must also be trusted by the remote TLS server.

Recommended client configuration:
RSA-2048 · PEM · unencrypted PKCS#1

RSA and ECDSA Can Be Used Together

An important distinction is the difference between the public key contained in a certificate and the algorithm used by the CA to sign that certificate.

An mTLS client certificate can contain an RSA-2048 public key while the certificate itself is signed using ECDSA.

For TCW242, TCW260, TCG120-4 and TCG140-4, an RSA-2048 client certificate signed using ECDSA-SHA256 by a P-256 intermediate CA is a compatible configuration.

The same principle applies to other parts of the TLS connection.

The client public key algorithm, certificate signature algorithm, TLS key exchange, and server certificate perform different cryptographic functions and do not need to use the same algorithm.

Keeping these roles separate is important when configuring and troubleshooting mTLS connections.

mTLS Client Certificate and Private Key Formats

Certificate compatibility is not only about the cryptographic algorithm. The certificate encoding and private key format also matter.

PEM vs. DER

PEM is a text-based format. A PEM certificate normally uses:

-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----

DER contains the same type of certificate data in binary form.

For TCW242, TCW260, TCG120-4 and TCG140-4, we use PEM encoding for the client certificate and private key.

PKCS#1 vs. PKCS#8

RSA private keys commonly use two different containers.

PKCS#1 is the traditional RSA-specific format. It normally starts with:

-----BEGIN RSA PRIVATE KEY-----

PKCS#8 is an algorithm-independent container. It normally starts with:

-----BEGIN PRIVATE KEY-----

For these Teracom devices, we recommend an unencrypted RSA private key in traditional PKCS#1 PEM format.

Our standard: RSA-2048 · PEM · unencrypted PKCS#1

mTLS Client Certificates Are Only Part of the Configuration

A valid client certificate and matching private key do not guarantee a successful TLS handshake.

The server configuration must also be compatible with the TLS capabilities of the device.

Several server-side settings are particularly important.

1. TLS 1.2 and ECDHE key exchange

The server should support TLS 1.2 and an ECDHE cipher suite capable of negotiating the secp256r1 or P-256 group.

Using an RSA client certificate does not remove elliptic curves from the TLS handshake.

The ECDHE group used for key exchange is independent of whether the client certificate contains an RSA or EC public key.

An RSA client certificate can therefore be used with ECDHE key exchange and with an ECDSA-signed server certificate.

In other words, RSA can be used for client authentication while elliptic curve cryptography is used elsewhere in the same TLS connection.

2. The device must trust the server

Mutual TLS authentication works in both directions.

The server must provide a valid certificate for the requested hostname together with the required intermediate certificates.

The Teracom device must also have the appropriate trusted CA certificate so that it can verify the server certificate.

A P-256 server certificate chain is compatible with TCW242, TCW260, TCG120-4 and TCG140-4 when used with an RSA-2048 client certificate signed by a P-256 intermediate CA.

This does not mean that every server or CA certificate must use P-256. It is one compatible configuration for these devices.

3. The server must trust the device

The other direction is equally important.

When client certificate authentication is required, the server must trust the CA that issued the client certificate.

A valid client certificate can still be rejected if its issuing CA is missing from the server’s trusted client CA list.

This type of failure can look like a certificate compatibility problem even when the certificate and private key are correct.

4. Client authentication signature algorithms matter

TLS 1.2 supports several RSA signature schemes.

When requesting a client certificate, the server should accept RSA PKCS#1 v1.5 signatures, for example:

rsa_pkcs1_sha256
rsa_pkcs1_sha384

The server should not require RSA-PSS exclusively.

This requirement concerns the signature generated by the client during TLS authentication. It is different from the signature algorithm used by the CA to sign the client certificate.

For example, the client can use RSA PKCS#1 v1.5 during authentication even when its RSA-2048 certificate was signed by the issuing CA using ECDSA-SHA256.

5. Make sure mTLS is actually mandatory

A server can accept client certificates without requiring them.

For true mTLS authentication, the server must be configured to require and verify the client certificate rather than simply accepting one when it is provided.

The connection should fail when the client does not provide a valid certificate issued by a trusted CA.

Recommended Configuration for mTLS Client Certificates

For TCW242, TCW260, TCG120-4 and TCG140-4, the following combination provides a practical common configuration:

Client public key: RSA-2048
Certificate encoding: PEM
Private key: unencrypted PKCS#1 RSA
TLS version: TLS 1.2
ECDHE group: P-256
Client authentication signatures: RSA PKCS#1 v1.5 supported by the server
Server certificate: valid certificate with required intermediate certificates
CA trust: configured on both the device and the server

An RSA-2048 client certificate signed using ECDSA-SHA256 by a P-256 intermediate CA, together with a P-256 server certificate chain, is a compatible combination for all four devices.

These requirements apply to the TLS connection itself, independently of the application protocol or service using it.

The Takeaway: mTLS Client Certificates

mTLS client certificates cannot be considered separately from the complete TLS configuration.

The client public key, certificate signature, private key format, TLS key exchange, server certificate, authentication signature algorithms, and CA trust configuration all play separate roles in establishing the connection.

For this reason, certificate support should be considered for specific devices rather than assumed for an entire product family.

Our conclusion

TCW242, TCW260, TCG120-4 and TCG140-4 can use a common RSA-2048 configuration for mTLS client certificates.

Using PEM certificates, unencrypted PKCS#1 RSA private keys, and compatible TLS server settings provides a consistent basis for deployments that combine these devices.

For other Teracom devices, certificate support should be checked individually according to their hardware and firmware capabilities.