Adding Application Connectors for ADC Devices

AppViewX supports creating an application connector for the following ADC device vendors:

  • A10
  • Array
  • AVI
  • Citrix
  • F5
  • HAProxy
  • NginxPlus
  • Radware
  1. Enter the General Information for the ADC devices.
    Table 1. Field descriptions for the Certificate Details
    Field Description
    *Category From the dropdown list, select ADC.

    If the certificate being pushed was enrolled with CSR generation at endpoint, this field is auto populated with the category selected at the time of certificate enrollment.
    *Vendor From the dropdown list, select the ADC device vendor (for the device to which this certificate will be pushed).

    If the certificate being pushed was enrolled with CSR generation at endpoint, this field is auto populated with the vendor selected at the time of certificate enrollment.
    *Connector Name Enter a name for this connector, to be able to identify it later.

    AppViewX recommends naming connectors according to use cases so they are easily distinguishable.

    Description Enter any additional details you want to record for this connector.
    Based on the information populated here, the SSL Templates/Server selection/Virtual server selection/SSL profiles section is populated with the list of available devices for the specified vendor that are already onboarded in AppViewX.
    Note: The name of this section is populated based on the Vendor selected.
  2. To select the device(s) to which the certificate will be pushed, under SSL templates, from the list of Available Devices, click .
    The Selected devices list is updated automatically.
  3. Enter the Certificate Details.
    Table 2. Field descriptions for the Certificate Details
    Field Description
    *Certificate Type From the dropdown list, select the file type of the certificate to be pushed.
    Activate Certificate To activate the certificate after it has been pushed, select this checkbox.
    Service Action From the dropdown list, select the required value:
    • Restart (stops and starts the process)
    • Reload (informs the daemon to reload only the configurations)
    • None
    Note: After device addition, if there are managed HAProxy certificates in the certificate inventory, by default, Service Action is set to None.
    *Certificate File Name Enter the file name of the certificate to be pushed. The file extension is auto-populated based on the Certificate Type selected.
    *Key File Name The private key associated with a certificate is stored in a key file.

    Enter the name of the file that contains the private key associated with the certificate to be pushed.

    The file extension .key is automatically populated.
    *Certificate Location Enter the path to the location on your local system where the certificate file to be pushed is stored.
    *Key Location The private key associated with a certificate is stored in a key file.

    In the Key Location field, enter the path to the location on your local system where the private key file for the certificate to be pushed is stored.
    *Certificate key pair name Enter the key-pair name used to identify the certificate and its associated private key.
    Enable SNI Push for Certificate To enable SNI push in the virtual server, select this checkbox.
    Enable SNI in Virtual Server To enable SNI in the virtual server, select this checkbox.
    Push Root and Intermediate Certificates To push the root and intermediate certificates, along with the end certificate, select this checkbox.

    For the Web Dispatcher server, this field is enabled by default and is non-editable.
    Service Restart To restart the device service immediately after the certificate is pushed, enable this checkbox.
    Private Key in Device If the private key associated with the certificate being pushed has been stored on a hardware device, select this checkbox.
  4. Enter the Push Details.
    Table 3. Field descriptions for the Push Details
    Field Description
    *Script Location Script files are commonly used to perform certain tasks required to be completed before and/or after a certificate is pushed to the target system.

    The script to be run before the certificate is pushed is called a pre-push script and the script to be run after the push is called a post-push script.

    From the following options, select the location of the script file(s):

    • In AppViewX
    • In Device
    Pre - Push Script File Name Enter the file name of the pre-push script.
    Important: Read the pre and push script usage instructions here.
    Pre - Push Script File Path This field is displayed when Script Location = In Device.
    Enter the location on your local system where the pre-push script file is stored.
    Important: Read the pre and push script usage instructions here.
    Post - Push Script File Name Enter the file name of the post push script.
    Important: Read the pre and push script usage instructions here.
    Post - Push Script File Path This field is displayed when Script Location = In Device.
    Enter the location on your local system where the post-push script file is stored.
    Important: Read the pre and push script usage instructions here.
    Overwrite The Overwrite option is used to specify if existing certificates on the target system will be overwritten with the certificate being pushed.

    If this option is enabled, the certificate being pushed will overwrite any existing certificates with the same identifier on the target system. This will also ensure that only the latest version of the certificate is available on the target system.

    If it is disabled, the push operation will fail in the event of conflicts with the certificates on the target system.
    Push Automatically To automatically push the certificate after it is renewed/reissued to the target system, enable this checkbox.
    Note: The auto push feature for a certificate works only if enabled for the certificate application connector as well the associated certificate group. To enable this feature at the certificate group level, refer the instructions here.
    Secure Push The Secure Push option ensures that the certificate is pushed to the target system securely, protected from any unauthorized access.
  5. Click Save.
    The connector is displayed on the certificate holistic view.