Applies only to SafeConsole OnPrem

Affects: SafeConsole Ready devices 4.1 and 4.2

The problem 

When using a CA issued SSL certificate from an intermediate CA, SafeConsole Ready devices will not be able to verify the trust of the certificate on certain systems for unknown reasons. 


The solution easiest to implement is to switch to a certificate generated by SafeConsole and push that as a trusted certificate according to the SafeConsole setup guide.

Workaround 1

If all intermediate CA certificates are placed in the trusted root certificate authorities store before connecting your SafeConsoleReady devices to SafeConsole the trusted chain will be verified and the drives will trust the server.

Workaround 2

Pre-provision the devices using the pre-provisioning tool. 

The issue is due to be resolved in the 4.7 release.