Microsoft Server

  1. On the certificate holistic view, click Add Connector.
  2. Enter the General Information for the connector.
    Table 1. Field descriptions for the connector General Information
    Field Description
    *Category From the dropdown list, select Server.

    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 Microsoft Server.

    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.
    Tip: 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 entered here, the Server selection section is populated with the list of available Windows Apache devices already onboarded in AppViewX.
  3. To select the device(s) to which the certificate will be pushed, from the dropdown list, select one of the following options:
    • MS Server
    • Exchange Server
    Note: If you have selected Exchange Server, profiles will be displayed in the format, Server type : Service name : Node details.
  4. Under Server selection, from the list of Available Devices, click .
    The Selected devices list is updated automatically.
  5. Enter the Certificate Details.
    Table 2. For MS Server: Field descriptions for the Certificate Details
    Field Description
    Location Type From the following options, select the location to which the certificate will be pushed:
    • File System (a storage location on your computer)
    • Certificate Store (a specialized location within the operating system for managing digital certificates)
    *Certificate Type From the dropdown list, select the file type of the certificate to be pushed.
    *Credential Type This field is displayed for the JKS certificates.

    From the dropdown list, select the source of the access credentials.
    *Push Location Enter the endpoint where the certificate will be pushed. This can be a network location or directory on the server, or a URL from where the server can retrieve the certificate.
    *Key File Name This field is displayed for the PEM, DER, and PKCS#7 certificates.

    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 File Name Enter the file name of the certificate to be pushed. The file extension is auto-populated based on the Certificate Type selected.
    *PFX Password This field is displayed for the PKCS#12 certificate types.

    Enter the password that will be required to access the .pfx and the .p12 certificate files.
    *KeyStore Password This field is displayed for JKS certificate types.

    Enter the password required to access the keystore that contains the JKS certificate to be pushed.
    Alias Name This field is displayed for the PKCS#12 and CERTDB certificate types.

    Enter the certificate alias assigned in the CSR generated for requesting/enrolling the certificate.

    Private key entry password This field is displayed for the JKS certificates.

    Enter the password required to decrypt the private key associated with the certificate.
    Push Root and Intermediate Certificates To push the root and intermediate certificates, along with the end certificates, select this checkbox.
    *Intermediate Certificate Alias Name 1

    This field is displayed only when Push Root and Intermediate Certificates is enabled.

    This field is not displayed for the JKS certificate types.

    Enter the alias name of the intermediate certificate file.
    *Root Certificate Alias Name

    This field is displayed only when Push Root and Intermediate Certificates is enabled.

    Enter the alias name of the root certificate file.
    Table 3. For Exchange Server: Field descriptions for the Certificate Details
    Field Description
    *Certificate Type The certificate type is defaulted to the following values
    • For AppViewX CSR generation - certificates which have private key, PKCS#12(*.p12) is the supported certificate format.
    • For Endpoint CSR generation PKCS#7(*.p7b) is the supported certificate format.
    *Friendly Name
    • For PKCS#7(*.p7b) certificate type, the friendly name is the common name of the certificate specified at the time of Endpoint CSR generation. During the push operation the common name is populated in the friendly name field (it is not editable).
    • For PKCS#12(*.p12) it is the user specified input.
    Services From the dropdown list, select one from the following services:
    • POP
    • IIS
    • SMTP
    • IMAP
    Restart Service This field is displayed only when Services = IIS.

    To restart the IIS service after the certificate is pushed, to ensure all changes have taken effect as required, select this checkbox.

    Note:

    When pushing certificates , the system now automatically selects the appropriate PKCS12 encryption algorithm based on the target Windows Server version:

    • Windows Server 2016 and earlier: Uses TripleDES encryption for compatibility
    • Windows Server 2019 and later: Uses the encryption algorithm from General Settings

    This is applicable for all service/devices such as Microsoft Server, Microsoft Exchange Server, Windows Gateway.

  6. Enter the Push Details.
    Table 4. 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.
  7. Click Save.
    The connector is displayed on the certificate holistic view.