Sorry I’m not of much help. The problem is that the Subject CN of the TV certificate is invalid, and there are no SAN’s defined.
Yours is:
CN = Samsung SmartViewSDK Cert. G2
Which is invalid as a CN. Mine is:
CN = SmartViewSDK
Which is valid, and is what the binding uses.
It’s hard to work around an invalid certificate in a binding (who knows, maybe Samsung will fix it) - I don’t know what those spaces are in the CN (spaces are not allowed in the Subject CN, but many browsers will ignore them), they may be null bytes caused by improper UDF-16 encoding.
If you try:
openssl s_client -connect 192.168.178.63:8002 2>/dev/null | openssl x509 -nameopt sep_comma_plus_space -text -noout
It might resolve the unknown white space. Which may or may not help.
You also can disable host validation for all of openhab (I think) by editing the file /etc/default/openhab and adding the following:
-Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true
To the end of EXTRA_JAVA_OPTS (with a space before it in the text string).
I don’t know if this really works, and it’s not recommended for production, but you could test it out.