Requirement
Description
The HTTP load balancer must support
URL rewrite.
The load balancer must be able to modify the URL path of the
request based on simple rules to remove or rename parts of
the path.
The HTTP load balancer must support
TLS 1.2.
Some services might not support TLS versions other than 1.2.
The HTTP load balancer must support at
least some of the listed ciphers when
interacting with back-end services.
• ECDHE-RSA-AES128-GCM-SHA256
• ECDHE-ECDSA-AES128-GCM-SHA256
• ECDHE-ECDSA-AES256-GCM-SHA384
• ECDHE-RSA-AES128-SHA256
• ECDHE-ECDSA-AES128-SHA256
• ECDHE-RSA-AES128-SHA
• ECDHE-ECDSA-AES128-SHA
• AES128-GCM-SHA256
• AES256-GCM-SHA384
• AES128-SHA
The HTTP load balancer must be able to
use TCP health checks.
The load balancer must be able to perform health checks of
Avaya Aura
®
Web Gateway servers using TCP responses. To
avoid leaving multple TCP sockets opened, you must be able
to configure TCP health checks to half-opened connections.
The external HTTP load balancer must
be able to use standard headers to
determine the FQDN from the original
request that is used to reach the system.
Avaya Aura
®
Web Gateway uses the “Host” header to identify
the FQDN that is used by the client to reach the system.
Note:
This behavior is required if the customer requires different
FQDNs per location or uses different FQDNs to reach the
system. If a single global FQDN is used, you can ignore
this requirement.
The external HTTP load balancer must
relay the client certificates.
This requirement is only needed for authenticating clients
using a client certificate.
The HTTP load balancer must be able to
insert custom headers to HTTP requests.
External load balancer requirements
October 2018
Deploying the Avaya Aura
®
Web Gateway
41
