See below for installing the Policy Agent on Linux.
Make sure you have completed the prerequisites described in Linux Installation Prerequisites.
Downloading the installation file
See below for installing the Policy Agent installation file.
To download the Policy Agent installation file
- Log in to the Cryptographic Security Platform Vault for VM Encryption webGUI or the Cryptographic Security Platform Vault for Databases webGUI with Cloud Admin privileges.
- Click Workloads.
- Click Actions > Download Policy Agent.
- Click the Download link associated with the following file:
hcs-client-agent-rel.number-build.number.run
Creating a certificate for the registration process
Create a certificate that you can install on the VM and use during the registration process.
Skip this section if you want to use Simplified or Automated Authentication.
To create a certificate for the registration process
- Select the Cloud VM Set with which you want to associate the VM.
- Click Actions > Create New Certificate.
- If desired, enter a passphrase for the certificate. If you enter a passphrase here, you will need to enter that passphrase when you install the certificate on the VM.
- Enter a date on which this certificate should expire.
Click Create. Cryptographic Security Platform Vault downloads a
.certfile to the default download location.Do not rename the downloaded certificate. The certificate name includes additional information, and a renamed certificate will fail.
Copying the installer
Copy the hcs-client-agent-rel.number-build.number.run installation file to the Linux machine.
Running the installer
Log in to the target Linux system as root, and run the following command in the directory containing the installation file.
$ sh ./hcs-client-agent-rel.number-build.number.run install [-y] [-P <installation_path>]Where:
-ytells the installer to use the/opt/hcsdefault installation directory without prompting.-Pspecifies the installation directory.
Make sure that you have executable permissions to /tmp because the installer extracts itself to the /tmp directory. If you get the following error:
./install.sh: Permission deniedUse the TMPDIR variable to select a different temporary directory. For example:
$ TMPDIR=$HOMEWhen uninstalling the Linux Policy Agent, you will also need to use a different directory.
The following example prompts the user for the installation directory.
$ sh ./hcs-client-agent-10.5.1-12345.runVerifying archive integrity... All good.Uncompressing hcs-client-agent.run.............HyTrust Agent will be installed in /opt/hcsSpecify location for installing HyTrust Agent (/opt/hcs): <Enter>Run once hcldStarting hcld... doneYou can now install online encryption driver, the process is described in the Admin GuidePlease see the following section of Admin Guide for details — Administration Guide > Data Encryption > Linux Encryption Overview Installation successfulThe following example installs the Policy Agent in the /opt/hcs default directory.
$ sh ./hcs-client-agent-10.5.1-12345.run install -yVerifying archive integrity... All good.Uncompressing hcs-client-agent.run.............HyTrust Agent will be installed in /opt/hcsRun once hcldStarting hcld... doneYou can now install online encryption driver, the process is described in the Admin GuidePlease see the following section of Admin Guide for details — Administration Guide > Data Encryption > Linux Encryption Overview Installation successfulThe following example installs the Policy Agent in the specified directory /opt/test without prompting:
$ sh ./hcs-client-agent-10.5.3-12345.run install -y -P /opt/testVerifying archive integrity... All good.Uncompressing hcs-client-agent.run.............HyTrust Agent will be installed in /opt/testRun once hcldStarting hcld... doneYou can now install online encryption driver, the process is described in the Admin GuidePlease see the following section of Admin Guide for details — Administration Guide > Data Encryption > Linux Encryption Overview Installation successfulRegistering the virtual machine into Vault.
Run the following command to register the virtual machine with Cryptographic Security Platform Vault.
hcl register [-a] [-h vm-name] [-d "vm-description"] [-p cert-passphrase] [-o one-time-passphrase] [-z cvm-set] [-v vault_id] [-n mapping-name] [-N] kc-hostname[:port],kc-hostname2[:port],... [cert-file.cert]Where:
-a—Indicates that you want to authenticate the VM through the command line or the script instead of through a certificate file. Use this option if you are using Simplified or Automated Authentication. If you created a certificate in Cryptographic Security Platform Vault, omit this option and specify the certificate name incert-file.cert.-c—Allows you to register this VM as a clone of the original VM.-h—The name of the VM that will be displayed in the Cryptographic Security Platform Vault webGUI (Default: hostname).-d—A description of the VM that will be displayed in the Cryptographic Security Platform Vault webGUI.-p—The passphrase assigned to the certificate when it was created. If you do not specify this parameter and the certificate has an associated passphrase, the registration process prompts you for the passphrase. Applies to Standard Authentication only.-v—The Vault ID of the Vault that will be displayed in Vault Management. If you do not specify the vault_id, you will be asked to enter vault_id.-o—The one-time passphrase that will be used to encrypt the initial communication between this VM and the existing Cryptographic Security Platform Vault cluster. If you do not specify this parameter, the registration process prompts you for the one-time passphrase. Applies to Standard Authentication only.The passphrase is valid for 15 minutes from the time it is created. Authenticate the VM in the Cryptographic Security Platform Vault during this time. Authentication will fail after the passphrase has expired.
-z—The name of the Cloud VM Set defined in the Cryptographic Security Platform Vault cluster to which you want to assign this VM. Applies to Simplified or Automated Authentication only (the-aoption must be specified on thehcl registercommand).-n—The name of the Cluster Node Mapping that you want to associate with this VM. If you do not specify this option and one or more Cluster Node Mappings have been configured, the Policy Agent prompts you to select a Node Mapping from the list. If you do not want to use a Node Mapping, you must manually respond to this prompt. This option is mutually exclusive with the-Noption, described below, and it requires that the-aoption must be specified on thehcl registercommand.-N—Tells the Policy Agent that you do not want to use a Cluster Node Mapping, even if one is available. If you specify both-Nand-n, the Policy Agent ignores the-noption and does not assign a Node Mapping to the VM. Applies to Simplified or Automated Authentication only (the-aoption must be specified on thehcl registercommand).kc-hostname[:port],kc-hostname2[:port],...(required) — The list of IP addresses or hostnames for the Cryptographic Security Platform Vault nodes with which you want to register the VM. You must specify at least one Cryptographic Security Platform Vault node in this list. You must also specify a port if the Cryptographic Security Platform Vault nodes use anything other than the default port (443).If you are using the
-noption to specify a Cluster Node Mapping, this IP address will be the Cryptographic Security Platform Vault node that the VM contacts to retrieve the Node Mapping information. After the Node Mapping has been retrieved, the Policy Agent ignores any other IP addresses in this list and only registers the VM with the Cryptographic Security Platform Vault nodes contained in the Node Mapping.cert-file.cert—The name of the certificate file you copied to the target system if you are using Standard Authentication. If you are running thehcl registercommand from a directory other than the one where the.certfile resides, specify the full path to the.certfile as part of this option. If you did not create a certificate file in Cryptographic Security Platform Vault, omit this option and use the-aoption instead.
The following command registers a VM with the "hq-vm-4" name, the "HQ Linux Server Alpha" description, and two nodes.
$ hcl register -h hq-vm-4 -d "HQ Linux Server Alpha" 10.238.32.74,10.238.32.75 ad85837b-9862-11e1-afd5-000c29de5d41_120507163538.certYou need to specify a passphrase that will be used for authenticationEnter passphrase (min 16 characters): Registered as hq-vm-4 with node(s) 10.238.32.74,10.238.32.75Please login to the node to complete the authentication of this nodeThe following command registers a VM without prompting the user.
$ hcl register -h hq-vm-4 -d "HQ Linux Server Alpha" -p <certpassphrase> -o <onetimepassword> 10.238.32.74,10.238.32.75 ./install/hytrust/cert/ad85837b-9862-11e1-afd5-000c29de5d41_120507163538.certRegistered as hq-vm-4 with node(s) 10.238.32.74,10.238.32.75Please login to the node to complete the authentication of this nodeThe following command registers a VM with the "hq-vm-4" name, the "HQ Linux Server Alpha" description, and prompts the user for the admin account information, the cloud VM Set, and the cluster node mapping.
$ hcl register -a -h hq-vm-4 -d "HQ Linux Server Alpha" 10.238.66.250Do you want to register into a Vault? (y/n) yPlease provide the vaultIDvaultid: d84243e7-d359-4179-9530-3497434e3192Please provide the login detailsusername: CloudAdminpassword: Available Cloud VM Sets--------------------------------------------------------------------------------SF-Datacenter--------------------------------------------------------------------------------Please specify Cloud VM Set to which this VM should be added: SF-DatacenterRegistered as hq-vm-4 with node(s) 10.238.66.250Completing authentication for hq-vm-4 on node(s) 10.238.66.250Authentication complete, machine ready to useGetting Mapping informationThis VM can be added to one of the following Mappings--------------------------------------------------------------------------------1 : SF-Datacenter-Map2 : West-Coast-Map--------------------------------------------------------------------------------Please select a numeric Mapping ID (0 to skip): 1Mapping: SF-Datacenter-Mapserver description First Node, ip 10.238.66.250, port 443server description Second Node, ip 10.238.66.251, port 443Updated list with nodes 10.238.66.250:443,10.238.66.251:443The following command sets the name, description, cloud VM set, and cluster node mapping without prompting user.
$ hcl register -a -h hq-vm-4 -v d84243e7-d359-4179-9530-3497434e3192 -d "HQ Linux Server Alpha" -z SF-Datacenter -n SF-Datacenter-Map 10.238.66.250Please provide the login detailsusername: CloudAdminpassword: Registered as hq-vm-4 with node(s) 10.238.66.250Completing authentication for hq-vm-4 on node(s) 10.238.66.250Authentication complete, machine ready to useGetting Mapping informationMapping: SF-Datacenter-Mapserver description First Node, ip 10.238.66.250, port 443server description Second Node, ip 10.238.66.251, port 443Updated list with nodes 10.238.66.250:443,10.238.66.251:443