![]() |
The TSAPI Service may be configured to provide Transport Layer Security (TLS) for encrypting data exchanged between the TSAPI client and the AE Services server. If you plan to use encrypted links, you have the option of using the Avaya Product Root Certificate Authority (CA) certificate which is default, or using certificates issued by a trusted in-house or third-party certificate authority (also referred to as your own certificates). For more information about certificates, see Appendix A: Certificates management.
![]() | Note |
You do not have to add any configuration settings for certificates under the following conditions: |
You do not use encrypted connections, and, hence, certificates.
You use encrypted Tlinks with the default AE Services certificate. The default AE Services certificate is signed by the Avaya Product Root Certificate Authority (CA). The certificate for the Avaya Product Root CA is installed with the TSAPI Linux client in /opt/mvap/tsapi/client/certs/CA/avayaprca.pem.
You use encrypted Tlinks with your own certificates, and you have copied the trusted CA certificate to the client computer as /opt/mvap/tsapi/client/certs/CA/aesCerts.pem. When establishing a secure connection, the TSAPI client checks to see if you have provided this file. If so, you do not need to configure the location of the Trusted CA File in the tslibrc file.