Avaya Aura® Device Services installation fails when using third-party CA identity certificates

Last Updated : Mar 08, 2024 |
Prolog information
Metadata
Keywords:

Condition

In an Avaya Aura® environment, Avaya Aura® Device Services installation fails if you use identity certificates signed by a third-party CA. The installation log contains entries related to issues with:
  • Certificate validation. For example: 
    Invalid format :Not able to validate certificateInappropriate certificate data
    
Failed to import certificate.
  • DRS service. For example: 
    Executing # Sending registration information to DRS master
    
ERROR # 1 : Sending registration information to DRS master. Terminating configuration process ..........
    
/opt/Avaya/DeviceServices/10.2.0.0.70/drs/8.1.3.5.0-38243-SDK-1.0/bin/start_aggregation.sh failed with exit code: 1, exiting...

Cause

Starting from Release 10.1.1, if you use identity certificates signed by a third-party CA, the Avaya Aura® Device Services trustore does not contain System Manager CA certificates. If you use identity certificates signed by a third-party CA, ensure that System Manager also uses an identity certificate signed by the same CA.

Solution

  1. Ensure that System Manager uses an identity certificate signed by the same CA that signs the Avaya Aura® Device Services identity certificates as described in Configuring third-party identity certificates for System Manager.