Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 6c6defd

Browse files
authoredFeb 17, 2022
remove preview
remove preview
1 parent 1afac47 commit 6c6defd

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed
 

‎articles/application-gateway/mutual-authentication-portal.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ services: application-gateway
55
author: mscatyao
66
ms.service: application-gateway
77
ms.topic: how-to
8-
ms.date: 04/02/2021
8+
ms.date: 02/18/2022
99
ms.author: caya
1010
---
1111

12-
# Configure mutual authentication with Application Gateway through portal (Preview)
12+
# Configure mutual authentication with Application Gateway through portal
1313

1414
This article describes how to use the Azure portal to configure mutual authentication on your Application Gateway. Mutual authentication means Application Gateway authenticates the client sending the request using the client certificate you upload onto the Application Gateway.
1515

@@ -27,14 +27,14 @@ First create a new Application Gateway as you would usually through the portal -
2727

2828
## Configure mutual authentication
2929

30-
To configure an existing Application Gateway with mutual authentication, you'll need to first go to the **SSL settings (Preview)** tab in the Portal and create a new SSL profile. When you create an SSL profile, you'll see two tabs: **Client Authentication** and **SSL Policy**. The **Client Authentication** tab is where you'll upload your client certificate(s). The **SSL Policy** tab is to configure a listener specific SSL policy - for more information, check out [Configuring a listener specific SSL policy](./application-gateway-configure-listener-specific-ssl-policy.md).
30+
To configure an existing Application Gateway with mutual authentication, you'll need to first go to the **SSL settings** tab in the Portal and create a new SSL profile. When you create an SSL profile, you'll see two tabs: **Client Authentication** and **SSL Policy**. The **Client Authentication** tab is where you'll upload your client certificate(s). The **SSL Policy** tab is to configure a listener specific SSL policy - for more information, check out [Configuring a listener specific SSL policy](./application-gateway-configure-listener-specific-ssl-policy.md).
3131

3232
> [!IMPORTANT]
3333
> Please ensure that you upload the entire client CA certificate chain in one file, and only one chain per file.
3434
3535
1. Search for **Application Gateway** in portal, select **Application gateways**, and click on your existing Application Gateway.
3636

37-
2. Select **SSL settings (Preview)** from the left-side menu.
37+
2. Select **SSL settings** from the left-side menu.
3838

3939
3. Click on the plus sign next to **SSL Profiles** at the top to create a new SSL profile.
4040

@@ -82,7 +82,7 @@ Now that we've created an SSL profile with mutual authentication configured, we
8282

8383
In the case that your client CA certificate has expired, you can update the certificate on your gateway through the following steps:
8484

85-
1. Navigate to your Application Gateway and go to the **SSL settings (Preview)** tab in the left-hand menu.
85+
1. Navigate to your Application Gateway and go to the **SSL settings** tab in the left-hand menu.
8686

8787
1. Select the existing SSL profile(s) with the expired client certificate.
8888

@@ -94,4 +94,4 @@ In the case that your client CA certificate has expired, you can update the cert
9494

9595
## Next steps
9696

97-
- [Manage web traffic with an application gateway using the Azure CLI](./tutorial-manage-web-traffic-cli.md)
97+
- [Manage web traffic with an application gateway using the Azure CLI](./tutorial-manage-web-traffic-cli.md)

0 commit comments

Comments
 (0)
Please sign in to comment.