Avaya Oceana® runs as applications within the Avaya Breeze® platform. For enhanced security, Avaya provides the ability to add or replace Trust and Identity Certificates. Identity Certificates are administered individually for Avaya clusters. Five default Identity Certificates are generated as part of the Avaya OVA deployment process. You can replace a default certificate with a certificate from a well-known Certificate Authority (CA).
The Security Module HTTPS certificate is visible to applications and endpoints. If you are using HTTPS with hostname validation checks, you must replace the default HTTP certificate. There are many ways of generating Identity Certificates for Avaya Oceana®. This section describes one of the methods of creating an Identity Certificate for each Avaya Oceana® cluster. The Identity Certificate for each cluster must include the following in the Subject Alternative Name (SAN) fields:
The entities that access Avaya through HTTPS must resolve the Common Name (CN) and SAN fields in the certificate with the FQDNs of the Avaya node. To resolve the certificate CN or SAN fields, enter the Management FQDN and SIP FQDN of each Avaya node in your DNS server. Also enter the Cluster FQDNs in your DNS server. In a cluster with a single node, the cluster FQDN is the SIP FQDN of the one node in the cluster.
