An enterprise client communicates with an API hosted in Azure API Management (APIM). You must implement two security requirements:
1. Validate that the client presents a client certificate containing an authorized thumbprint.
2. Accept the subscription key in a custom HTTP header named `X-API-Signature` instead of the default header.
Which two configuration actions should you perform to meet these requirements?
- Configure the `validate-client-certificate` policy in the `inbound` section of the API policy configuration, specifying the allowed client certificate thumbprints.Answer
- Configure the API settings in the Azure portal or ARM template to use the custom HTTP header named `X-API-Signature` for subscription key validation.Answer
- CAdd the `validate-client-certificate` policy to the `outbound` section of the API policy configuration.
- DConfigure the `authentication-certificate` policy in the inbound section, referencing a certificate stored in Azure Key Vault without configuring Key Vault access policies to grant the APIM instance GET permissions.
Answer
Configure the validate-client-certificate policy in the inbound section of the API policy configuration, and configure the API settings to use the custom HTTP header for subscription key validation.
To secure the APIM endpoint with the client certificate, you must configure the validate-client-certificate policy within the inbound section of the policy file. Additionally, to change the header name where APIM expects the subscription key, you must modify the Subscription key header name setting in the API settings configuration.
Step-by-Step Solution
Key Concept
Securing APIM gateway endpoints using client certificates and customizing subscription key validation headers.
Estimated Time:2m 0s