Operations
This section provides information on operations that a ProtectV Server Administrator performs on the CipherTrust Manager. These operations include registering ProtectV clients with the CipherTrust Manager, enrolling them with the ProtectV service, and protecting data stored on a ProtectV client.
Tip
Registration and enrollment can be performed on the CipherTrust Manager or the ProtectV clients.
On the CipherTrust Manager, registration is a two-step process involving registration and enrollment, as described in this document.
On the ProtectV clients, registration is a one-step process using the Registration Utility (pvreg) installed with the ProtectV software on ProtectV clients. Refer to "Registering ProtectV Linux Clients" and "Registering ProtectV Windows Clients" in the ProtectV Clients User's Guide.
Registering ProtectV Clients
Registration is the process of configuring a ProtectV client with a CipherTrust Manager. This process creates SSL certificates for further communication between the CipherTrust Manager and the ProtectV client.
Registering a ProtectV client with the CipherTrust Manager requires a registration token and the fingerprint of the server’s web interface certificate. These are used as parameters during the ProtectV client's registration with the CipherTrust Manager. Single registration token can be used to register any number of ProtectV clients.
The following diagram shows the process of registering ProtectV clients with the CipherTrust Manager:
By default, CipherTrust Manager issues a Local CA with Common Name "KeySecure Root CA" which is used by ProtectV for signing client certificates. This Local CA is, by default, marked as trusted by the "web" interface that is also used by ProtectV for client authentication. Make sure that the CA whose signature is used for registering ProtectV clients is trusted by the "web" interface. Refer to Interfaces for details.
Note
To use the CipherTrust Manager's proxy instead of the CipherTrust Manager for registering ProtectV clients, you need to configure the proxy, as explained in Using Proxy with ProtectV Clients. After the proxy is configured, ProtectV clients can be registered with the proxy instead of the CipherTrust Manager.
Enrolling ProtectV Clients
After a ProtectV client is registered with the CipherTrust Manager, it must be enrolled with the ProtectV service for protection of data stored on them.
A registered ProtectV client can be enrolled with the ProtectV service by using the enroll API. Specify the ID and the cloud ID of the registered ProtectV client.
