The Avaya Aura® Device Services server has multiple options for certificate management, which include:
Importing local or public certificates.
Importing local certificates that are signed by an intermediate Certificate Authority.
Viewing the details for a certificate.
The following sections outline the manual command line and configuration utility processes for setting up certificates during the Avaya Aura® Device Services installation process. After you import a certificate, you must restart Avaya Aura® Device Services for the changes to take effect.
You can also manage and update certificates using the Avaya Aura® Device Services web administration portal. For more information about working with the web administration portal, see Administering Avaya Aura® Device Services.
Important:
The web administration portal is the preferred method for managing certificates. Use the configuration utility process to configure certificates for troubleshooting purposes, but after this is done, perform certificate management from the web administration portal when possible.
For information about managing the Avaya Aura® Device Services root certificate and for managing identity certificates, see Administering Avaya Aura® System Manager.
If you do not use Avaya Aura® System Manager certificates, the Avaya Aura® Device Services server requires four PEM certificates and their corresponding key files:
The REST interface certificate is used for the communication with the clients.
The OAMP interface certificate is used for the OAMP GUI.
The node certificate is used for internode communication such as cluster notifications. The node certificate is also used for encrypting database traffic.
Avaya Aura® Device Services supports PKS12-format certificates. The signing authority certificate file is also required.
Important:
All certificates must contain Subject Alternate Names for the FQDN of the Avaya Aura® Device Services server and the FQDN of the local Avaya Aura® Device Services node.
The Common Name of the Node certificate must contain the FQDN of the local Avaya Aura® Device Services node. In a cluster, every Avaya Aura® Device Services node has a different FQDN.
