Skip to content

Commit 8969fde

Browse files
committed
typos
1 parent 722aac0 commit 8969fde

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

articles/api-management/api-management-howto-mutual-certificates-for-clients.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,9 +15,9 @@ ms.custom: engagement-fy23
1515

1616
# How to secure APIs using client certificate authentication in API Management
1717

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.
1919

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).
2121

2222
For a conceptual overview of API authorization, see [Authentication and authorization in API Management](authentication-authorization-overview.md#gateway-data-plane).
2323

@@ -39,18 +39,18 @@ Using key vault certificates is recommended because it helps improve API Managem
3939
* If you have not created an API Management service instance yet, see [Create an API Management service instance](get-started-create-service-instance.md).
4040
* 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.
4141

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.
4343

4444
> [!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.
4646
4747
[!INCLUDE [api-management-client-certificate-key-vault](../../includes/api-management-client-certificate-key-vault.md)]
4848

4949
## Enable API Management instance to receive and verify client certificates
5050

5151
### Developer, Basic, Standard, or Premium tier
5252

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.
5454

5555
![Negotiate client certificate](./media/api-management-howto-mutual-certificates-for-clients/negotiate-client-certificate.png)
5656

articles/api-management/api-management-howto-mutual-certificates.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ author: dlepow
88

99
ms.service: api-management
1010
ms.topic: article
11-
ms.date: 01/04/2023
11+
ms.date: 01/12/2023
1212
ms.author: danlep
1313
ms.custom: devx-track-azurepowershell, engagement-fy23
1414
---
@@ -41,10 +41,10 @@ Using key vault certificates is recommended because it helps improve API Managem
4141
* 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.
4242

4343
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.
4545

4646
> [!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.
4848
* [Disable certificate chain validation](#disable-certificate-chain-validation-for-self-signed-certificates)
4949

5050
[!INCLUDE [api-management-client-certificate-key-vault](../../includes/api-management-client-certificate-key-vault.md)]

includes/api-management-client-certificate-key-vault.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.author: danlep
1212

1313
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).
1414

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.
1616

1717
[!INCLUDE [api-management-key-vault-access](./api-management-key-vault-access.md)]
1818

0 commit comments

Comments
 (0)