Skip to content

Commit 100e4c0

Browse files
authored
Merge pull request #92715 from cjpluta/patch-3
Proposing information on trusted root certificate
2 parents 33e6e68 + 5918c33 commit 100e4c0

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/application-gateway/configuration-http-settings.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,12 @@ This setting combined with HTTPS in the listener supports [end-to-end TLS](ssl-o
4646

4747
This setting specifies the port where the back-end servers listen to traffic from the application gateway. You can configure ports ranging from 1 to 65535.
4848

49+
## Trusted root certificate
50+
51+
If you select HTTPS as the back-end protocol, the Application Gateway requires a trusted root certificate to trust the back-end pool for end-to-end SSL. By default, the **Use well known CA certificate** option is set to **No**. If you plan to use a self-signed certificate, or a certificate signed by an internal Certificate Authority, then you must provide the Application Gateway the matching public certificate that the back-end pool will be using. This certificate must be uploaded directly to the Application Gateway in .CER format.
52+
53+
If you plan to use a certificate on the back-end pool that is signed by a trusted public Certificate Authority, then you can set the **Use well known CA certificate** option to **Yes** and skip uploading a public certificate.
54+
4955
## Request timeout
5056

5157
This setting is the number of seconds that the application gateway waits to receive a response from the back-end server.

0 commit comments

Comments
 (0)