I’m working on a scenario where I need to implement mutual TLS (mTLS) using X.509 certificates over TCP. My requirement is that both client and server must authenticate each other during the TLS handshake, and the connection must fail if a valid client certificate is not presented. Specifically, I’m trying to understand: Does LabVIEW currently support client certificate authentication? Is it possible to enforce mTLS (i.e. reject connections when the client cert is missing or untrusted), rather than it being optional? The current shipping LabVIEW example shows only one-way authentication."C:\Program Files\National Instruments\LabVIEW 2026\examples\Data Communication\Protocols\TLS\TLS Client and Server with Self-Signed Server Certificate.vi"If anyone has implemented something similar, I would love to connect and talk more about this.Thanks!Jatin

mTLS support with LabVIEW

My requirement is that both client and server must authenticate each other during the TLS handshake, and the connection must fail if a valid client certificate is not presented.

Specifically, I’m trying to understand:

Does LabVIEW currently support client certificate authentication?
Is it possible to enforce mTLS (i.e. reject connections when the client cert is missing or untrusted), rather than it being optional?

The current shipping LabVIEW example shows only one-way authentication.

"C:\Program Files\National Instruments\LabVIEW 2026\examples\Data Communication\Protocols\TLS\TLS Client and Server with Self-Signed Server Certificate.vi"

If anyone has implemented something similar, I would love to connect and talk more about this.

Thanks!
Jatin