JBoss

  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 JBoss.

    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 SSL templates section is populated with the list of available JBoss devices already onboarded in AppViewX.
  3. 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.
  4. Enter the Certificate Details.
    Table 2. Field descriptions for the Certificate Details
    Field Description
    Use Existing Configuration If the Use Existing Configuration option is enabled,the existing server.xml file is used to create the application connector. (By default, this option is selected.)

    If it is disabled, the server configuration XML file will be overwritten with the values specified in the fields below (displayed only if this option is disabled).
    Certificate Type This field is displayed when Use Existing Configuration is enabled.

    From the dropdown list, select the file type of the certificate to be pushed.
    *KeyStore Location This field is displayed when Use Existing Configuration is enabled and Certificate Type = JKS (*.jks).

    For JKS certificates, a keystore is a repository used for storing private keys and certificates.

    In the KeyStore Location field, enter the path to the location on your local system where the JKS keystore file, for the certificate to be pushed, is stored.
    *Password This field is displayed when Use Existing Configuration is enabled and Certificate Type = JKS (*.jks).

    Enter the password required to access the keystore file for the JKS certificate to be pushed.

    *Alias Name This field is displayed when Use Existing Configuration is enabled and Certificate Type = Default JKS (*.jks) or JKS (*.jks).

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

    Private Key in Device If the private key associated with the certificate being pushed has been stored on a hardware device, select this checkbox.
  5. 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.
    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.
  6. Click Save.
    The connector is displayed on the certificate holistic view.