Open micaelmbagira opened 2 years ago
Since no one replied so far... can you try whittling this down to a minimal test case, like calling tls.connect()
in a loop?
My hunch is that this is a problem with the PKCS#11 plugin you're using to make your keys and certificates available, not node, but there's currently not enough information to say for sure.
Version
16.13.1
Platform
arm9
Subsystem
imx6 with Trusted Platform Module
What steps will reproduce the bug?
The issue happens when
tls.connect
(first connection works fine)tls.connect
are{'cert': '/path/to/tpmCert.pem', 'privateKeyEngine': '/usr/lib/engines-1.1/pkcs11.so', 'privateKeyIdentifier': 'foo', 'ca': '/path/to/root.ca.pem'}
How often does it reproduce? Is there a required condition?
The initial connection works fine but after ~1 hour, mqtt reconnects to the server using
tls.connect
again with the same options as for the initial connection.What is the expected behavior?
The secure connection should be established with the given certificates.
What do you see instead?
Additional information
No response