Skip to content

Commit 4517647

Browse files
authored
Merge pull request #94606 from RegExpresso/main
Fixed typo
2 parents 0520115 + 7828c9c commit 4517647

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/application-gateway/certificates-for-backend-authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In this article, you learn how to:
2222

2323
## Prerequisites
2424

25-
An existing backend certificate is required to generate the authentication certificates or trusted root certificates required for allowing backend instances with Application Gateway. The backend certificate can be the same as the TLS/SSL certificate or different for added security. Application Gateway doesn't provide you any mechanism to create or purchase an TLS/SSL certificate. For testing purposes, you can create a self-signed certificate but you shouldn't use it for production workloads.
25+
An existing backend certificate is required to generate the authentication certificates or trusted root certificates required for allowing backend instances with Application Gateway. The backend certificate can be the same as the TLS/SSL certificate or different for added security. Application Gateway doesn't provide you any mechanism to create or purchase a TLS/SSL certificate. For testing purposes, you can create a self-signed certificate but you shouldn't use it for production workloads.
2626

2727
## Export authentication certificate (for v1 SKU)
2828

@@ -100,4 +100,4 @@ The following steps help you export the .cer file for your certificate:
100100

101101
## Next steps
102102

103-
Now you have the authentication certificate/trusted root certificate in Base-64 encoded X.509(.CER) format. You can add this to the application gateway to allow your backend servers for end to end TLS encryption. See [Configure end to end TLS by using Application Gateway with PowerShell](./application-gateway-end-to-end-ssl-powershell.md).
103+
Now you have the authentication certificate/trusted root certificate in Base-64 encoded X.509(.CER) format. You can add this to the application gateway to allow your backend servers for end to end TLS encryption. See [Configure end to end TLS by using Application Gateway with PowerShell](./application-gateway-end-to-end-ssl-powershell.md).

0 commit comments

Comments
 (0)