Using Private Keys in PKI
Private keys play a large role in public-key infrastructure (PKI) with the . They secure communications between nodes at the message or transport level, within multiple areas of the Gateway.
gateway83
Private keys play a large role in public-key infrastructure (PKI) with the
API Gateway
. They secure communications between nodes at the message or transport level, within multiple areas of the Gateway.Contents:
Listen Ports
Private keys are used in SSL-enabled communications that are inbound to the Gateway. When you specify a private key for an inbound listen port, this assigns an identity to that listen port. When applications open a TCP connection with the Gateway on this port, they see the certificate for this private key. This makes it important that you assign a private key that is expected by external entities.
For information about assigning private keys to a listen port, see Listen Port Properties.
You cannot assign a private key to a listen port that is not enabled for SSL/TLS. For example, the default port “8080” does not use SSL/TLS, so you cannot assign a private key to it.
Policy Assertions
Many assertions support SSL/TLS functions and you can assign private keys to them. This allows the Gateway to present a particular identity for a certain purpose. For example, routing assertions can use a particular private key to present a specific identity to an end point. Certain assertions can sign or encrypt elements of a message to ensure integrity and confidentiality.
For information about how to assign a private key to an assertion, see Select a Custom Private Key.