End-to-End SSL with Azure Application Gateway
I created the following diagram to help explain the configuration and flow of end-to-end SSL with Azure Application Gateway. For a more detailed description, please refer to the Azure documentation Overview of end to end SSL with Application Gateway.
Here’s a brief description of each step:
- The user browses to https://www.abc.com
- The client machine performs a DNS lookup on www.abc.com
- DNS returns the IP address 184.108.40.206
- The browser connects to 220.127.116.11 which is the frontend IP address of the Application Gateway. The Application Gateway is configured with an SSL Policy that requires a minimum version of TLS and a supported set of Cipher suites.
- Application Gateway routes the request to the appropriate Listener
- The Listener is configured with an SSL certificate for the custom doman (e.g. www.abc.com) and terminates the SSL connection
- Application Gateway applies Rules to route the request to the appropriate Backend
- The Backend is configured to use HTTPS to connect to the backend servers. In addition, the Backend must contain the public key of the backend site certificate (e.g. backend.abc.com). This public key is uploaded as a .cer file and stored in the backend authentication certificate list. Application Gateway will only connect to backend sites for which it has the public key in its backend authentication certificate list.
- Application Gateway sends the request
- Application Gateway connects to the backend using HTTPS
Azure Quickstart Template - Application Gateway with WAF, end to end SSL, two IIS servers and HTTP to HTTPS redirection