Closed jensflorian closed 3 years ago
The Exception is causes by this line of code https://github.com/stefan-kaestle/openhab2-addons/blob/59165a5bc2c822910658bc181a18f0bc6ac987eb/bundles/org.openhab.binding.boschshc/src/main/java/org/openhab/binding/boschshc/internal/devices/bridge/BoschSslUtil.java#L167 But I have currently no glue why loading the PEM resource file from the Jar fails.
Creating a jks file manually is not really possible - you need to follow all the steps and use exactly the same values as the code in createKeyStore()
.
After tests with my own setup (OH3, RPi Linux, Bosch SHC v1.0 Beta 4) I can confirm that this a reproducible bug and not related to OsX. I get exactly the same log traces.
I was able to find the changes in 82ab755eae34da6a77bbced0d921a60ba41e7a7d causing the problem that the *.pem files can't be loaded anymore from the Jar and will provide soon a bug fix branch where the two resources will be located inside the now expected package org.openhab.binding.boschshc.internal.devices.bridge
.
Thanks a lot @jensflorian for reporting the bug and for the very useful trace.
FYI @coeing, we need to include this fix into the openhab PR
Thanks for the update, will be happy to test again after the fix.
Fixed with PR #60 and will be part of v1.0 of the Bosch SHC binding.
Expected Behavior
Keystore is created after entering IP and PW into bridge handler.
Current Behavior
No *.jks file is created. After setting log to trace I get this info:
Possible Solution
Create jks file manually (how?)
Steps to Reproduce (for Bugs)
Reproducible. I assume creation of jks file in OsX shell may be different from RaspberryPI.
Your Environment