Entrust CA
Prerequisites
- An Entrust client authentication certificate and credentials−API username
(username) and API key (password) having necessary access for CLM
actions.To get a private key + certificate that can be used to access to API. The general steps performed by a super admin are:
- Generate a new private TLS/SSL key and a CSR.
- Issue a certificate in the ECS account using the CSR. Client Authentication must be enabled in the certificate.
- Import the private key and certificate into the system that will be invoking the API.
- Test that TLS/SSL mutual authentication is successfully configured.
- AppViewX server should either have internet access or have a proxy configured in AppViewX general settings.
Configuring Entrust
-
Go to
(Menu) > SIGN+ > ADMINISTRATION > Certificate
Authority.
-
From the displayed CA, Select Entrust.
The Entrust home page is displayed. The Entrust tab is selected by default.
-
Click the Configure Now button or +Add icon from the middle
or top-right of the page respectively.
The Entrust configuration page is displayed.

-
Update the following details in the General Information section as
described in the table:
Table 1. General Information - Field Description Table Fields Description *CA Account name A unique name to identify the CA setting. Note: No special characters other than ‘.’, ‘-’,’_’ are allowed. Names should not start with special characters.*Purpose/Usage Certificate Type for which CLM actions will be enabled. For example: Server and Client
Proxy Required Enable this field if the CA communication needs to happen via Proxy. The proxy details configured in general settings will be used for communication. Data Center (AppViewX's CA agent) Select the data center through which the CA communication needs to happen. *: Mandatory fields -
Update the following details in the CA Configuration section as
described in the table. These fields are necessary for invoking the Entrust
CA APIs for Certificate Management.
Table 2. CA Configuration - Field Description Table Fields Description *Client Authentication The client authentication certificate from Entrust for API communication. Note: Must be a valid <.p12> file.To generate an CSR within AppViewX refer to Generating a CSR and download the CSR. Further, upload the CSR to the Entrust homepage as described in section - XXXXX.
*Base URL This URL will contain just the hostname of the Entrust CA instance. The value is https://api.entrust.net/enterprise/v2 User Name Enter the API Username to communicate with the CA. Password Enter the API Password to communicate with the CA. Auto Approve Select the checkbox to avoid queuing of new certificates in the CA portal. *: Mandatory fields -
Update the following details in the Advanced Settings section as
described in the table.
Table 3. Advanced Settings - Field Description Table Fields Description Poll after CSR Submission A check box field when selected will fetch the certificated immediately after CSR Submission on enrollment, renew, and reissue of certificate with the retry count and retry frequency as described below. *Retry Count The number of times the polling will take place after CSR submission. Enter a value between 1 and 10. *Retry Frequency The duration of the polling. enter the value between 1 and 30seconds *: Mandatory fields -
Click Fetch Custom Attributes.
The attributes available for the CA account will be fetched from the Certificate Authority along with the CA and profile names. A pop-up message is displayed as CA and profiles fetched.
-
Click Save.
The created Entrust configuration settings will be added. A pop-up message is displayed as <CA_name> Settings Added.
Validating Entrust CA
-
Go to
(Menu) > SIGN+ > ADMINISTRATION > Certificate
Authority.
-
From the displayed CA, Select Entrust.
The Entrust home page is displayed.
-
In the Status column of the grid with the listed accounts, click
Check to validate the CA setting that has been
created.
The CA communication will be validated and the Connection Status will be shown as either Success or Failure.
