You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-mutual-certificates-for-clients.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,9 @@ ms.custom: engagement-fy23
15
15
16
16
# How to secure APIs using client certificate authentication in API Management
17
17
18
-
API Management provides the capability to secure access to APIs (i.e., client to API Management) using client certificates and mutual TLS authentication. You can validate certificates presented by the connecting client and check certificate properties against desired values using policy expressions.
18
+
API Management provides the capability to secure access to APIs (that is, client to API Management) using client certificates and mutual TLS authentication. You can validate certificates presented by the connecting client and check certificate properties against desired values using policy expressions.
19
19
20
-
For information about securing access to the backend service of an API using client certificates (i.e., API Management to backend), see [How to secure back-end services using client certificate authentication](./api-management-howto-mutual-certificates.md).
20
+
For information about securing access to the backend service of an API using client certificates (that is, API Management to backend), see [How to secure back-end services using client certificate authentication](./api-management-howto-mutual-certificates.md).
21
21
22
22
For a conceptual overview of API authorization, see [Authentication and authorization in API Management](authentication-authorization-overview.md#gateway-data-plane).
23
23
@@ -39,18 +39,18 @@ Using key vault certificates is recommended because it helps improve API Managem
39
39
* If you have not created an API Management service instance yet, see [Create an API Management service instance](get-started-create-service-instance.md).
40
40
* You need access to the certificate and the password for management in an Azure key vault or upload to the API Management service. The certificate must be in **PFX** format. Self-signed certificates are allowed.
41
41
42
-
If you use a self-signed certificate, also [install a CA root certificate](api-management-howto-ca-certificates.md) in your API Management instance.
42
+
If you use a self-signed certificate, also install trusted root and intermeidate [CA certificates](api-management-howto-ca-certificates.md) in your API Management instance.
43
43
44
44
> [!NOTE]
45
-
> CA root certificates for certificate validation are not supported in the Consumption tier.
45
+
> CA certificates for certificate validation are not supported in the Consumption tier.
## Enable API Management instance to receive and verify client certificates
50
50
51
51
### Developer, Basic, Standard, or Premium tier
52
52
53
-
To receive and verify client certificates over HTTP/2 in the Developer, Basic, Standard, or Premium tie,s you must enable the **Negotiate client certificate** setting on the **Custom domain** blade as shown below.
53
+
To receive and verify client certificates over HTTP/2 in the Developer, Basic, Standard, or Premium tiers, you must enable the **Negotiate client certificate** setting on the **Custom domain** blade as shown below.
@@ -41,10 +41,10 @@ Using key vault certificates is recommended because it helps improve API Managem
41
41
* You need access to the certificate and the password for management in an Azure key vault or upload to the API Management service. The certificate must be in **PFX** format. Self-signed certificates are allowed.
42
42
43
43
If you use a self-signed certificate:
44
-
*[Install a CA root certificate](api-management-howto-ca-certificates.md) in your API Management instance.
44
+
* Install trusted root and intermediate [CA certificates](api-management-howto-ca-certificates.md) in your API Management instance.
45
45
46
46
> [!NOTE]
47
-
> CA root certificates for certificate validation are not supported in the Consumption tier.
47
+
> CA certificates for certificate validation are not supported in the Consumption tier.
Copy file name to clipboardExpand all lines: includes/api-management-client-certificate-key-vault.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.author: danlep
12
12
13
13
To create or import a certificate to the key vault, see [Quickstart: Set and retrieve a certificate from Azure Key Vault using the Azure portal](../articles/key-vault/certificates/quick-create-portal.md).
14
14
15
-
* Enable a system-assigned or user-assigned [managed identity](../articles/api-management/api-management-howto-use-managed-service-identity.md) in the API Management instance.
15
+
1. Enable a system-assigned or user-assigned [managed identity](../articles/api-management/api-management-howto-use-managed-service-identity.md) in the API Management instance.
0 commit comments