Rabbit MQServer
-
On the certificate holistic view, click Add
Connector.
-
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 RabbitMQServer. 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 Rabbit MQServer devices already onboarded in AppViewX. -
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. -
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. *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.
*Intermediate Location Enter the path to the location on your local system where the intermediate certificate file (for the end certificate being pushed) is stored. Private key passphrase Enter the password required to access the private key file. Private key in device If the private key associated with the certificate being pushed has been stored on a hardware device, select this checkbox. -
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. -
Click Save.
The connector is displayed on the certificate holistic view.
What's Next
- To push a server certificate to a device, see Pushing a Server Certificate to a Device.
