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/application-gateway/mutual-authentication-portal.md
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@ services: application-gateway
5
5
author: mscatyao
6
6
ms.service: application-gateway
7
7
ms.topic: how-to
8
-
ms.date: 04/02/2021
8
+
ms.date: 02/18/2022
9
9
ms.author: caya
10
10
---
11
11
12
-
# Configure mutual authentication with Application Gateway through portal (Preview)
12
+
# Configure mutual authentication with Application Gateway through portal
13
13
14
14
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.
15
15
@@ -27,14 +27,14 @@ First create a new Application Gateway as you would usually through the portal -
27
27
28
28
## Configure mutual authentication
29
29
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).
31
31
32
32
> [!IMPORTANT]
33
33
> Please ensure that you upload the entire client CA certificate chain in one file, and only one chain per file.
34
34
35
35
1. Search for **Application Gateway** in portal, select **Application gateways**, and click on your existing Application Gateway.
36
36
37
-
2. Select **SSL settings (Preview)** from the left-side menu.
37
+
2. Select **SSL settings** from the left-side menu.
38
38
39
39
3. Click on the plus sign next to **SSL Profiles** at the top to create a new SSL profile.
40
40
@@ -82,7 +82,7 @@ Now that we've created an SSL profile with mutual authentication configured, we
82
82
83
83
In the case that your client CA certificate has expired, you can update the certificate on your gateway through the following steps:
84
84
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.
86
86
87
87
1. Select the existing SSL profile(s) with the expired client certificate.
88
88
@@ -94,4 +94,4 @@ In the case that your client CA certificate has expired, you can update the cert
94
94
95
95
## Next steps
96
96
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