If you plan to deploy Avaya Aura® Device Services in an environment without Avaya Aura®, obtain the following certificates before installing Avaya Aura® Device Services:
-
The third-party root CA certificate in the PEM format in a file with the root.pem file name.
-
One or more intermediate CA certificates in the PEM format concatenated into a single certificate chain in a file with the intermediate.pem file name.
-
An identity certificate signed by the CA. The Common Name and Subject Alternative Names parameters of the certificate must contain the following values:
-
The certificate format is PEM or PKCS12.
-
Common Name: The external load balancer FQDN or the Avaya Aura® Device Services virtual IP FQDN.
-
Subject Alternative Names:
-
FQDNs of all Avaya Aura® Device Services nodes in your deployment.
-
If you want to use the Utility Server: The virtual FQDN of the Utility Server.
Note:
In cloud environments, such as Microsoft Azure, Google Cloud Platform, or AWS, this is the FQDN of the external load balancer.
-
If you want to use the onboard Open LDAP: the localhost.localdomain record for IPv4 and the localhost6.localdomain record for IPv6.
-
A third-party CA-signed identity certificate chain to be used for Avaya Aura® Device Services. The certificate chain must be in the PKCS12 format in a file with the identity.p12 file name. The chain must consist of the identity certificate followed by all intermediate CA certificates in a reverse chain order.
Most third-party CAs use root and intermediate CAs to sign identity certificates. As a result, you must import identity and trust certificate chains to Avaya Aura® Device Services in the PKCS12 format.
