After deploying the Hitachi VSP service in CryptoHub, set up a client endpoint. An endpoint is a device authorized to access the service. Use the Endpoints menu to view and manage these devices.Documentation Index
Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
Use this file to discover all available pages before exploring further.
In the Add Endpoint dialog:
- Enter a Name for the endpoint (optional).
- Leave set the CryptoHub Hostname that is auto-populated.
Select [ Add Endpoint ]. The browser prompts you to download a zip file which contains the following files:
| File | Description |
|---|---|
ca-chain.pem | CA certificate bundle |
client-cert.pem | Client TLS certificate |
credential.txt | Contains the name of the identity CryptoHub created for the Hitachi VSP to use when connecting and authenticating via KMIP |
info.txt | Includes the service name and address for connecting to the CryptoHub |
pki.p12 | Full Client PKI in encrypted PKCS #12 format (contains the CA chain, client certificate, and client private key) |
pki-password.txt | Contains the password for the PKCS #12 file |
CryptoHub <number>.cer | Auto-generated self-signed CA certificate used to issue client endpoint TLS certs (number is random) |
Futurex Test Root CA (ECC).cer or Futurex Test Root SSL CA.cer | Futurex Test Root CA for embedded Futurex Test TLS certs (ECC or RSA, based on the algorithm configured for the KMIP connection pair) |
<number>-Prod-App-Alt.cer | KMIP server TLS certificate (number is random) |
The Hitachi VSP requires the client certificate in PKCS #12 format. The
pki.p12 file from the endpoint zip can be used directly, or you can generate a custom client certificate with x509v3 extensions as described in the next step.