Using "Manage Private Keys" for SSL Certificates

When you configure your gateway using the for the first time, a default self-signed key is generated based on the cluster hostname. This key is used for:
gateway83
When you configure your
CA API Gateway
using the Gateway Main Menu (Appliance) for the first time, a default self-signed key is generated based on the cluster hostname. This key is used for:
  • inbound connections
  • HTTP routing assertions for the client certificate (if necessary)
  • signatures in the policy
Use the Manage Private Keys task to view and manage this default key and all other keys:
Once you have created your private keys, you can use them in various ways in the Gateway.