CA-signed and self-signed certificates FAQ for SANtricity System Manager
This FAQ can help if you're just looking for a quick answer to a question.
Why does the Cannot Access Other Controller dialog box appear?
When you perform certain operations related to CA certificates (for example, importing a certificate), you might see a dialog box prompting you to accept a self-signed certificate for the second controller.
In storage arrays with two controllers (duplex configurations), this dialog box sometimes appears if SANtricity System Manager cannot communicate with the second controller or if your browser cannot accept the certificate during a certain point in an operation.
If this dialog box opens, click Accept Self-Signed Certificate to proceed. If another dialog box prompts you for a password, enter your Administrator password used for accessing System Manager.
If this dialog box appears again and you cannot complete a certificate task, try one of the following procedures:
-
Use a different browser type to access this controller, accept the certificate, and continue.
-
Access the second controller withSystem Manager, accept the self-signed certificate, and then return to the first controller and continue.
How do I know what certificates need to be uploaded to SANtricity System Manager for external key management?
For external key management, you import two types of certificates for authentication between the storage array and the key management server so the two entities can trust each other.
A client certificate validates the storage array's controllers, so the key management server can trust their Key Management Interoperability Protocol (KMIP) requests.
To obtain a client certificate, you use System Manager to complete a CSR for the storage array. You can also generate a CSR externally using a private and public key pair.
You can then upload the CSR to a key management server and generate a client certificate from there. Once you have a client certificate, copy that file to the host where you are accessing System Manager.
A key management server certificate validates the key management server, so the storage array can trust its IP address. Retrieve the server certificate file from the key management server, and then copy that file to the host where you are accessing System Manager.
What do I need to know about certificate revocation checking?
SANtricity System Manager allows you to check for revoked certificates by using an Online Certificate Status Protocol (OCSP) server, instead of uploading Certificate Revocation Lists (CRLs).
Revoked certificates should no longer be trusted. A certificate might be revoked for several reasons; for example, if the Certificate Authority (CA) improperly issued the certificate, a private key was compromised, or the identified entity did not adhere to policy requirements.
After you establish a connection to an OCSP server in System Manager, the storage array performs revocation checking whenever it connects to an AutoSupport server, External Key Management Server (EKMS), Lightweight Directory Access Protocol over SSL (LDAPS) server, or a Syslog server. The storage array attempts to validate these servers' certificates to ensure that they have not been revoked. The server then returns a value of "good," "revoked," or "unknown" for that certificate. If the certificate is revoked or the array cannot contact the OCSP server, the connection is refused.
|
Specifying an OCSP responder address in System Manager or in the command line interface (CLI) overrides the OCSP address found in the certificate file. |
What types of servers will revocation checking be enabled for?
The storage array performs revocation checking whenever it connects to an AutoSupport server, External Key Management Server (EKMS), Lightweight Directory Access Protocol over SSL (LDAPS) server, or a Syslog server.