Apache application object

Defines the data necessary for Trust Protection Platform to provision certificates to network devices in the PEM format used by Apache application servers.

Attributes that are not shown here may be inherited from one or more parent classes:

Class Name: Apache
Driver Name: appapache
Inheritance: Parent class—Application Base

Apache attributes
Attribute	Description
Application ID UI: Application ID Required: Yes	Policy Definable: Yes. Default: NA The Apache application ID. The Application ID must be a member of the CyberArk Safe with rights to the Safe.
Certificate Chain File UI: Certificate Chain File Required: No	Policy Definable: Yes. Default: NA The full path and filename on the managed device where Trust Protection Platform should write the applicable root and intermediate certificates.
Certificate File UI: Certificate File Required: Yes	Policy Definable: Yes. Default: NA The full path and filename on the managed device where Trust Protection Platform should write the certificate.
Client Tools Path UI: Client Tools Path Required: No	Policy Definable: Yes. Default: NA Required for remote key generation. The directory path where the toolkit on the device is located.
File Validation Disabled UI: NA Required: No	Policy Definable: No. Default: 0 The setting to control file validation: 0 = Validate. Authenticate to the managed device using assigned credentials. 1 = Disable validation.
Network Validation Disabled UI: NA Required: No	Policy Definable: Yes. Default: 0 The setting for network validation: 0 = Validate by making an SSL/TLS connection to the managed device. 1 = Disable network validation.
OCS Identifier UI: OCS Identifier Required: No	Policy Definable: No. Default: NA For remote key generation. The Operation Card Set (OCS) identifier.
Overwrite Existing Chain UI: Overwrite Existing Chain Required: No	Policy Definable: Yes. Default: 0 A value of 1 specifies that Trust Protection Platform should overwrite the existing certificate chain file when it installs a new certificate and private key.
Partition Password Credential UI: NA Required: No	Policy Definable: No. Default: NA A password credential that represents the PIN for the HSM partition where the private key is stored.
Private Key File UI: Private Key File Required: Yes	Policy Definable: Yes. Default: NA The full path and filename on the managed device where Trust Protection Platform should write the private key.
Private Key Label UI: Private Key Alias Required: No	Policy Definable: No. Default: NA Read-only. Only enabled for the nCipher nShield HSM option. Contains the HSM key alias for the Private Key. The format is (YYMMDDhhmmss) and file name of the key (without the file extension). For example 210316142039_MyPrivateKey.
Private Key Location UI: Private Key Location Required: Yes	Policy Definable: Yes. Default: NA The location where you want the remotely generated key pairs to be created: Device (Default), Thales SafeNet HSM ornCipher nShield HSM.
Protection Type UI: Protection Type Required: No	Policy Definable: Yes. Default: NA Required for remote key generation. The level of protection: Module, Softcard , or Operation Card Set
Slot Number UI: Port Required: No	Policy Definable: Yes. Default: NA The slot location on the HSM.
Softcard Identifier UI: Softcard Identifier Required: No	Policy Definable: No. Default: NA For remote key generation. Works in conjunction with a Protection TypeSoftcard. Requires a 40-character hash.