Skip to content

Commit 9584ad7

Browse files
committed
edits, image border
1 parent d9d58ee commit 9584ad7

File tree

2 files changed

+8
-9
lines changed

2 files changed

+8
-9
lines changed

articles/app-service/app-service-web-configure-tls-mutual-auth.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,10 @@ ms.custom: devx-track-csharp, devx-track-extended-java, devx-track-js, devx-trac
1111
---
1212
# Configure TLS mutual authentication in Azure App Service
1313

14-
You can restrict access to your Azure App Service app by enabling different types of authentication for it. One way to set up authentication is to request a client certificate when the client request is over TLS/SSL and to validate the certificate. This mechanism is called Transport Layer Security (TLS) mutual authentication or client certificate authentication. This article shows how to set up your app to use client certificate authentication.
14+
You can restrict access to your Azure App Service app by enabling different types of authentication for the app. One way to set up authentication is to request a client certificate when the client request is sent by using Transport Layer Security (TLS)/Secure Sockets Layer (SSL) and to validate the certificate. This mechanism is called *mutual authentication* or *client certificate authentication*. This article shows you how to set up your app to use client certificate authentication.
1515

1616
> [!NOTE]
17-
> Your app code is responsible for validating the client certificate. App Service doesn't do anything with this client certificate other than forwarding it to your app.
17+
> Your app code is responsible for validating the client certificate. App Service doesn't do anything with this client certificate other than forward it to your app.
1818
>
1919
> If you access your site over HTTP and not HTTPS, you don't receive any client certificates. If your application requires client certificates, you shouldn't allow requests to your application over HTTP.
2020
@@ -102,7 +102,7 @@ When you enable mutual auth for your application, all paths under the root of yo
102102
> [!NOTE]
103103
> Using any client certificate exclusion path triggers TLS renegotiation for incoming requests to the app.
104104
105-
1. On the left menu of your app's management pane, select **Configuration** > **General Settings**.
105+
1. On the left menu of your app management page, select **Configuration** > **General Settings**.
106106

107107
1. Next to **Certificate exclusion paths**, select the edit icon.
108108

@@ -112,7 +112,7 @@ When you enable mutual auth for your application, all paths under the root of yo
112112

113113
In the following screenshot, any path for your app that starts with `/public` doesn't request a client certificate. Path matching isn't case specific.
114114

115-
![Certificate Exclusion Paths][exclusion-paths]
115+
:::image type="content" source="media/app-service-web-configure-tls-mutual-auth/exclusion-paths.png" alt-text="Screenshot that shows setting a certificate exclusion path.":::
116116

117117
## Client certificate and TLS renegotiation
118118

@@ -126,7 +126,7 @@ For some client certificate settings, App Service requires TLS renegotiation to
126126
127127
To disable TLS renegotiation and to have the app negotiate client certificates during TLS handshake, you must configure your app with *all* these settings:
128128

129-
1. Set client certificate mode to "Required" or "Optional."
129+
1. Set the client certificate mode to **Required** or **Optional**.
130130
1. Remove all client certificate exclusion paths.
131131

132132
### Upload large files with TLS renegotiation
@@ -136,7 +136,7 @@ Client certificate configurations that use TLS renegotiation can't support incom
136136
To address the 100-KB limit, consider these alternative solutions:
137137

138138
1. Disable TLS renegotiation. Update your app's client certificate configurations with *all* these settings:
139-
- Set the client certificate mode to either "Required" or "Optional."
139+
- Set the client certificate mode to **Required** or **Optional**.
140140
- Remove all client certificate exclusion paths.
141141
1. Send a HEAD request before the PUT/POST request. The HEAD request handles the client certificate.
142142
1. Add the header `Expect: 100-Continue` to your request. This causes the client to wait until the server responds with a `100 Continue` before sending the request body, which bypasses the buffers.
@@ -166,7 +166,7 @@ public class Startup
166166
public void ConfigureServices(IServiceCollection services)
167167
{
168168
services.AddControllersWithViews();
169-
// Configure the application to use the protocol and client ip address forwarded by the frontend load balancer
169+
// Configure the application to use the protocol and client ip address forwarded by the front-end load balancer
170170
services.Configure<ForwardedHeadersOptions>(options =>
171171
{
172172
options.ForwardedHeaders =
@@ -176,7 +176,7 @@ public class Startup
176176
options.KnownProxies.Clear();
177177
});
178178

179-
// Configure the application to client certificate forwarded the frontend load balancer
179+
// Configure the application to client certificate forwarded the front-end load balancer
180180
services.AddCertificateForwarding(options => { options.CertificateHeader = "X-ARR-ClientCert"; });
181181

182182
// Add certificate authentication so when authorization is performed the user will be created from the certificate
@@ -623,4 +623,3 @@ def hellocert(request):
623623

624624
---
625625

626-
[exclusion-paths]: ./media/app-service-web-configure-tls-mutual-auth/exclusion-paths.png
-3.57 KB
Loading

0 commit comments

Comments
 (0)