Invalid/wrong device cert in credential throws warning, connection proceeds

[tjamison]

Connecting to a backend server via TLS, client displays this info in log:

2016-07-06 14:27:12.748 [warning] <0.139.0>@authorize_keys:process_cred_struct_:555 Wrong device_cert in cred
<<... (certificate) ...>>
<<... (certificate) ...>>
2016-07-06 14:27:12.749 [info] <0.116.0>@rvi_log:store_event:350 RVI_LOG: <<"conn:19-8fEt">>/1/<<"authorize">>/<<"cred stored 15eca337 Conn={<<"192.168.18.76">>,<<"9007">>}">>
2016-07-06 14:27:12.749 [info] <0.203.0>@dlink_tls_rpc:connection_authorized:739 dlink_tls:authorize(): Announcing local services: [] to remote "192.168.18.76":9007

Snipped certificate is indeed not the certificate presented for the handshake. However, the connection proceeds as if the credentials checked out OK.

Expected behavior is to terminate connection upon receiving invalid credentials.