If you are planning to connect Avaya Aura® Device Services to the Avaya Aura® Web Gateway, you need to use a certificate containing information about the FQDN that is used for server-to-server communication. Otherwise, this FQDN will not be part of the SAN, and Avaya Aura® Device Services will not connect to the Avaya Aura® Web Gateway.
Before you begin
When deploying a CloudFormation stack, provide the host name that is mapped directly to the Avaya Aura® Device Services nodes in the Hostname for server-to-server field. For more information, see Amazon Web Services deployments in Deploying Avaya Aura® Device Services.
Procedure
Log in to the Avaya Aura® Device Services web administration portal with the Security administrator role.
Navigate to Security Settings > Certificate Management > Identity Certificates.
In the Certificate Signing Requests area, click Create.
In the Create Certificate Signing Request window, click Show Advanced Settings.
Select Specifcy SAN Manually.
Select Add FQDN and provide the following SANs:
Load Balancer FQDN.
FQDN that is used for server-to-server communication.
FQDNs of all nodes in the cluster.
For example, an Avaya Aura® Device Services cluster with three nodes uses aads for the stack name and aadsrv for the server-to-server communication host name. The domain is aadsrv.ca.avaya.com. In this case, the CSR must contain the following SANs:
aads.ca.avaya.com for the load balancer.
aadsrv.ca.avaya.com for server-to-server communication.
aads0.ca.avaya.com for the first node in the cluster.
aads1.ca.avaya.com for the second node in the cluster.
aads2.ca.avaya.com for the third node in the cluster.
