CP4I: List of Issuers, CA certificates, and secrets

A summary of certificate issuers, with the CA issued by each, and the corresponding secret used to sign certificates in an API Connect deployment with IBM Cloud Pak for Integration (CP4I).

Table 1 presents a list of the certificate issuers used in an API Connect deployment, with the CA issued by each, and the corresponding secret used to sign certificates. In the table, the names of items use the variable APIC_instance_name, which should be replaced with the name of your deployed API Connect instance.

The APIC_instance_name-self-signed is used only for creating CAs, and does not have a corresponding certificate or secret of its own.

Table 1. Issuers, CAs, and secrets
Issuer	CA certificate	Secret
`APIC_instance_name-self-signed`	N/A	N/A
`APIC_instance_name-ingress-issuer`	`APIC_instance_name-ingress-ca` issued by `APIC_instance_name-self-signed`	`APIC_instance_name-ingress-ca`
`APIC_instance_name-a7s-ca`	`APIC_instance_name-a7s-ca` issued by `APIC_instance_name-self-signed`	`APIC_instance_name-a7s-ca`
`APIC_instance_name-mgt-ca`	`APIC_instance_name-mgt-ca` issued by `APIC_instance_name-self-signed`	`APIC_instance_name-mgt-ca`
`APIC_instance_name-ptl-ca`	`APIC_instance_name-ptl-ca` issued by `APIC_instance_name-self-signed`	`APIC_instance_name-ptl-ca`