My understanding on SSL certificates is this:
Public certificate: it can be public certificate of consumer application, CA gateway and backed system which will be shared with each other systems so that there would be SSL communication between these systems
Private Certificate or key: The certificate or key used by the consumer application/gateway/backend system to generate their own public certificates (self signed or Certificate Authority signed). Same private certificate or key will be used to validate incoming request to system and have successful SSL communication
When I open the ca-api-gateway-9-4.pdf documentation, I see two topics under "Working with SSL Certificates" page no.133, one "Manage Private Keys for SSL certificate" page no.133 and another one is "Manage certificates for ssl certificates" page no.140. In both the topics naming conventions used for keys and certificates are confusing and I am not able to understand how can I achieve below 3 scenarios. Also the way sequence of steps mentioned under these topics are confusing to achieve the same below 3 scenarios. It seems that "key" keyword is used for private key and somewhere key keyword is used for ssl certificate.
Can you please clarify on the naming conventions used in these topics. It would be good if you suggest the topics in this document ca-api-gateway-9-4.pdf to achieve below 3 scenarios.
In my project we have 2-way SSL communication between inbound system, gateway and outbound systems. Our requirements are as below: