How might one go about configuring and troubleshooting this? I've replaced /nvram/cacert.pem with my root and intermediate. In a packet capture, I see the client connecting and then disconnecting after the TLS handshake begins. Where can one get some log information from the client to help diagnose what the problem is?
Hi, I have recently installed the RDK-B on a Raspberry Pi and want to connect it to the ACS through HTTPS. However, every time that it tries to establish the connection it appears that is not able to validate the certificate authority by default.
6 Comments
Z-Alexei Pastuchov
yes, it does
Z-Z-Sangeetha Mariappan
Yes, connection to ACS server is secured in RDK-B.
Z-Chad Clark
Just to clarify, is this referring to TLS client certificate authentication support?
Z-Z-Sangeetha Mariappan
Yes, this is referring to TLS client certificate authentication
Z-Chris Turner
How might one go about configuring and troubleshooting this? I've replaced /nvram/cacert.pem with my root and intermediate. In a packet capture, I see the client connecting and then disconnecting after the TLS handshake begins. Where can one get some log information from the client to help diagnose what the problem is?
Z-Nuno Barros
Hi,
I have recently installed the RDK-B on a Raspberry Pi and want to connect it to the ACS through HTTPS. However, every time that it tries to establish the connection it appears that is not able to validate the certificate authority by default.
Logs:
[mod=TR69, lvl=WARN] [tid=16874] OpenSSL: error:14090086:lib(20):func(144):reason(134)
[mod=TR69, lvl=WARN] [tid=16874] Certificate not verified - ACS unable to get local issuer certificate
Although, when I use the "curl" command to perform a request to the same HTTPS URL, I can confirm that the TLS handshake is properly exchange.
Could it be possible to have some guidance/clarifications on how I can setup the HTTPS connection?