You are configuring a connection to a custom backend API from an Azure API Management (APIM) instance. The backend API is hosted on-premises and secured using a TLS/SSL certificate signed by a private internal Certificate Authority (CA) that is not publicly trusted. When APIM attempts to forward requests to the backend API, the connection fails with an HTTP 500 error due to a TLS handshake failure. You need to resolve the error and ensure that APIM can establish a secure TLS connection to the backend API while maintaining strict TLS validation. Which of the following actions should you perform?
- Upload the public root CA certificate to the Certificates section of the API Management instance.Cevap
- BCreate a custom backend resource in API Management and set the skipCertificateChainValidation property to true in the backend configuration.
- CStore the root CA certificate in an Azure Key Vault and grant the API Management system-assigned managed identity the GET permission to Key Vault secrets.
- DAdd the authentication-certificate policy to the inbound processing section of the API and reference the thumbprint of the client certificate.
Cevap
Upload the public root CA certificate to the Certificates section of the API Management instance.
Uploading the public root CA certificate of the private Certificate Authority to the Certificates section of the API Management instance allows the gateway to build the trust chain and validate the backend certificate. This resolves the TLS handshake failure while maintaining strict validation.
Adım Adım Çözüm
Anahtar Kavram
Configuring trusted CA certificates in Azure API Management to secure backend communication.