Configuring AppViewX PKIaaS

  1. Go to menu > KUBE+ > CLUSTER PKI > Certificate Authority
  2. Click the +Add icon on the top right of the page.
  3. Select the AppViewX PKIaaS in the left side vendor list.
  4. Update the following details in the General Information section as described in the table.
    Table 1. General Information - Field Description Table
    Name Description Validation
    *Name A unique name to identify the CA setting No special characters other than ‘.’, ‘-’,’_’ are allowed. The name should not start with special characters.
    *Purpose/Usage Certificate Type for which CLM actions will be enabled. For example, server and clients NA
    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. NA
    Data Center Select the data center through which the CA communication needs to happen. NA
    Note: The asterisk (*) symbol indicates a mandatory field.
  5. Update the following details in the CA Configuration section as described in the table.
    Options Description
    *Region Region of the certificate.
    *Configure With The method of certificate type to upload.
    *Upload JSON Option to upload the certificate file.
    *Email Address Email address of the user.
    *Project Id ID of the project.
    Note: The asterisk (*) symbol indicates a mandatory field.
  6. Select Fetch Procedures.
    Note: The procedures available in the AppViewX PKIaaS CA account will be fetched and listed for the specific user.
  7. To map the fetched procedures, click on one or many and click the Actions dropdown:
    1. CASE 1 - If the user selects Server only in Purpose and Usage, then the fetched procedure by default will be of server/client both. The Action dropdown will only have - Map as Server. and MAP as Default
    2. CASE 2 - If the user selects Client only in Purpose and Usage, then the fetched procedure by default will be of server/client both. The Action dropdown will only have - Map as Client. and MAP as Default
    3. CASE 3 - If the user selects Server and Client both in Purpose and Usage, then the fetched procedure by default will be of server/client both. The Action dropdown will have both the actions Map as Client , Map as Server, and MAP as Default
  8. Click Save.