Avaya Aura® MS includes default certificates that are useful for demonstration purposes. To ensure production systems are not compromised, you must replace the default certificates with unique, trusted certificates. Options for certificate replacement are:
Certificates signed by a trusted party Certificate Authority (CA).
Certificates signed and created by you using an authoritative certificate, including root certificates generated by Avaya Aura® System Manager.
Use the following table as an aid for the security configuration procedures in this section:
Definitions for default service profiles |
Service profile name |
Interface secured |
Application |
Connections with applications, such as VXML or an application server. |
Clustering |
Avaya Aura® MS internode connections in clusters. |
EM |
Element Manager (EM) connections for administrator web browser access. |
OAM |
Web services, such as those accessed using SOAP with Avaya Aura® MS, and remote database access. |
Signaling |
SIP and MRCPv2 connections with Avaya Aura® MS. |
