Public Key Infrastructure (PKI) combines software, encryption technologies, and services to enable enterprises to secure their communications and transactions over data networks. A successful PKI provides the management infrastructure to integrate public key technology into your IT infrastructure. Public key technology includes digital certificates, public keys, and certificate authorities.
The sending process, or person is actually the originator.
The receiving process, or person is the intended recipient.
Data integrity is not compromised.
Avaya uses standard X.509 PKI to manage certificates in the enterprise in which the hierarchy of certificates is always a top-down tree, with a root certificate at the top, representing the central Certificate Authority (CA) that is integral to the trusted-party scheme and does not need third-party authentication.
The Avaya product PKI is limited to authentication between devices primarily to automatically establish a TLS or similar connection to ensure confidentiality, integrity, and authenticity. VoIP devices that use Avaya software or need to establish a TLS connection with other devices that are manufactured or distributed by Avaya (or used in coordination with Avaya products) use certificates issued by CAs or downloads from Signing Authorities (SAs) under the Avaya Product PKI.
Private key located in /etc/opt/ecs/certs/cm/private/server.key
Certificate located in /etc/opt/ecs/certs/cm/ID/server.crt
Trusted CA certificates located in /etc/opt/ecs/certs/cm/CA/all-ca.crt
The table lists the Avaya public and private keys and their uses.
| Entity | Key type | Uses |
|---|---|---|
| Subscriber | Private key |
In some cases the subscriber private key is used specifically for signing code. |
| Relying party | Public key |
|
Note The Avaya Product Certificate Authority does not:
Publish subscriber certificates, but it does archive copies of certificates Notify other entities of certificates that it has issued
Issue certificates to individuals