Fix callhome device "DISCONNECTED" status 37/110637/3
authorOleksandr Zharov <oleksandr.zharov@pantheon.tech>
Mon, 11 Mar 2024 15:58:51 +0000 (16:58 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Wed, 13 Mar 2024 13:48:53 +0000 (14:48 +0100)
commit8d9520165054769ecf91c4ab9cd2afde5969fd58
tree1ff008d42f28b5731f258f26b60b15662afa5700
parent3830698b5b7c415a06f40ea68061f82c5a8052e0
Fix callhome device "DISCONNECTED" status

Fixed error when callhome device always has status "DISCONNECTED"
after adding it to allowed devices. This issue arose after refactoring
AuthorizedKeysDecoder class to use plain KeyStore access to acquire
provides. New code did not specify what exact provider we want to use
and thus caused confusion - instead of Bouncy Castle KeyFactory that
was used before new code returned Sun KeyFactory. That result in next
issue with searching for valid host key when adding new device and
all other errors that described in logs attached to Jira ticket.

JIRA: NETCONF-1249
Change-Id: I5689fa6ad173a5b7cd99f0210a366b77db74b0d5
Signed-off-by: Oleksandr Zharov <oleksandr.zharov@pantheon.tech>
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
apps/callhome-provider/src/main/java/org/opendaylight/netconf/topology/callhome/AuthorizedKeysDecoder.java