Closed coeing closed 3 years ago
@GerdZanker I think this is fixed with your last pull request, isn't it?
Yes, its avoided with PR #70, because the keystore password is now a static password defined in code. The BoschSHC systempassword is only used for pairing.
Drawback: A new keystore will be created using your SHC IP address and a new pairing is needed.
A change of SHC "system password" is an issue and happening also during initial setup of the binding e.g. if the wrong password was used instead of the App password.
See also comments in openhabCommunity.
The current solution is to *delete the/etc/oss_openhabbinding .jks file in your openhab installation** because the binding will recreate the jks file.
TODO from
BoschSslUtil.java
:In the meantime the initial pull request is discussed and from comments we can use "reference" code from openhab core how certificate handling is done there. See CertificateGenerator.java and the generateCertificate() function how the password, and self singed cert creation is done.
With this reference we should get rid of password problems, by using a single fixed password ins the code and avoid at least the
bcprov-jdk15on
bundle dependency, which increases the jar size a lot.