Digital certificates certify that a public key belongs to its reputed owner. To ensure greater trust, a trusted party can sign the public key and the information about its owner, creating a public-key certificate, usually called a certificate. Similar to a driver’s license, a certificate guarantees the identity of its bearer.
A trusted party that issues digital certificates is called a certification authority (CA), similar to a governmental agency that issues drivers’ licenses. A CA can be an external certification service provider or even a government, or the CA can belong to the same organization as the entities it serves. CAs can also issue certificates to other sub-CAs, which creates a tree-like certification hierarchy called a public-key infrastructure (PKI).
Server certificate signed by a Remote Feature Activation (RFA) Issuing Authority (IA)
RFA IA certificate signed by the Avaya Product Root Certificate Authority (CA)
Root certificate for the Avaya Product CA
The server certificate and the IA certificate are embedded in the authentication file along with the private key associated with the certificate. The Avaya Product Root CA certificate is embedded in the Messaging software base.
FIPS 140-2 level 4 certified cryptographic module to sign media server certificates.
Generate public/private key pairs using OpenSSL
Obtain digital certificates for media server certificates
Retrieve a copy of the IA certificate The secure hardware and daemon ensure that media server certificates are stored securely, are used only for the purpose of signing authorized certificates, and are protected from unauthorized access or duplication.