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-overview.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.topic: conceptual
9
9
ms.author: caya
10
10
11
11
---
12
-
# Overview of mutual authentication with Application Gateway (Preview)
12
+
# Overview of mutual authentication with Application Gateway
13
13
14
14
Mutual authentication, or client authentication, allows for the Application Gateway to authenticate the client sending requests. Usually only the client is authenticating the Application Gateway; mutual authentication allows for both the client and the Application Gateway to authenticate each other.
15
15
@@ -68,7 +68,7 @@ For more information on how to extract trusted client CA certificate chains, see
68
68
69
69
## Server variables
70
70
71
-
With mutual authentication, there are additional server variables that you can use to pass information about the client certificate to the backend servers behind the Application Gateway. For more information about which server variables are available and how to use them, check out [server variables](./rewrite-http-headers-url.md#mutual-authentication-server-variables-preview).
71
+
With mutual authentication, there are additional server variables that you can use to pass information about the client certificate to the backend servers behind the Application Gateway. For more information about which server variables are available and how to use them, check out [server variables](./rewrite-http-headers-url.md#mutual-authentication-server-variables).
Copy file name to clipboardExpand all lines: articles/application-gateway/overview-v2.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ The new v2 SKU includes the following enhancements:
23
23
-**Static VIP**: Application Gateway v2 SKU supports the static VIP type exclusively. This ensures that the VIP associated with the application gateway doesn't change for the lifecycle of the deployment, even after a restart. There isn't a static VIP in v1, so you must use the application gateway URL instead of the IP address for domain name routing to App Services via the application gateway.
24
24
-**Header Rewrite**: Application Gateway allows you to add, remove, or update HTTP request and response headers with v2 SKU. For more information, see [Rewrite HTTP headers with Application Gateway](./rewrite-http-headers-url.md)
25
25
-**Key Vault Integration**: Application Gateway v2 supports integration with Key Vault for server certificates that are attached to HTTPS enabled listeners. For more information, see [TLS termination with Key Vault certificates](key-vault-certs.md).
26
+
-**Mutual Authentication (mTLS)**: Application Gateway v2 supports authentication of client requests. For more information, see [Overview of mutual authentication with Application Gateway](mutual-authentication-overview.md).
26
27
-**Azure Kubernetes Service Ingress Controller**: The Application Gateway v2 Ingress Controller allows the Azure Application Gateway to be used as the ingress for an Azure Kubernetes Service (AKS) known as AKS Cluster. For more information, see [What is Application Gateway Ingress Controller?](ingress-controller-overview.md).
27
28
-**Performance enhancements**: The v2 SKU offers up to 5X better TLS offload performance as compared to the Standard/WAF SKU.
28
29
-**Faster deployment and update time** The v2 SKU provides faster deployment and update time as compared to Standard/WAF SKU. This also includes WAF configuration changes.
@@ -70,6 +71,7 @@ The following table compares the features available with each SKU.
70
71
| Rewrite HTTP(S) headers ||✓|
71
72
| URL-based routing |✓|✓|
72
73
| Multiple-site hosting |✓|✓|
74
+
| Mutual Authentication (mTLS) ||✓|
73
75
| Traffic redirection |✓|✓|
74
76
| Web Application Firewall (WAF) |✓|✓|
75
77
| WAF custom rules ||✓|
@@ -110,4 +112,4 @@ An Azure PowerShell script is available in the PowerShell gallery to help you mi
110
112
111
113
Depending on your requirements and environment, you can create a test Application Gateway using either the Azure portal, Azure PowerShell, or Azure CLI.
112
114
113
-
-[Tutorial: Create an application gateway that improves web application access](tutorial-autoscale-ps.md)
115
+
-[Tutorial: Create an application gateway that improves web application access](tutorial-autoscale-ps.md)
Copy file name to clipboardExpand all lines: articles/application-gateway/rewrite-http-headers-url.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
@@ -126,7 +126,7 @@ Application gateway supports the following server variables:
126
126
| ssl_enabled | "On" if the connection operates in TLS mode. Otherwise, an empty string. |
127
127
| uri_path | Identifies the specific resource in the host that the web client wants to access. This is the part of the request URI without the arguments. Example: In the request `http://contoso.com:8080/article.aspx?id=123&title=fabrikam`, uri_path value will be `/article.aspx`|
128
128
129
-
### Mutual authentication server variables (Preview)
129
+
### Mutual authentication server variables
130
130
131
131
Application Gateway supports the following server variables for mutual authentication scenarios. Use these server variables the same way as above with the other server variables.
0 commit comments