Description

This article describes and issue where the managed host addition fails with the message as below.

 

Error While adding Managed Host

Cannot connect to the host check password and IP.

Symptoms

The System and License Management shows the below error during the addition of the managed host to the console

The /var/log/qradar.log shows the following errors when the host is being added.

 

Screenshot 2024-09-04 at 1.07.59 PM.png

 

The /var/log/secure log file has the following error message while the managed host is being added. 

Sep 2 02:54:06 x.x.x.x sshd[265296]: error: Received disconnect from x.x.x.x port 39270:3: java.security.InvalidKeyException: java.lang.SecurityException: Signers of 'org.bouncycastle.crypto.params.AsymmetricKeyParameter' do not match signers of other classes in package [preauth] security.provider.12=org.bouncycastle.jce.provider.BouncyCastleProvider

Solution

The error is caused by a conflicting .jar file in deployments that were initially installed in JSA 7.3

 

The following steps need to be followed to remove the JAR file conflicts.:

 

  1. Use SSH to log in to the JSA Console as the root user.
  2. Create a backup directory:
    mkdir -pv /store/support
    
  3. Move the conflicting .jar file to the backup directory:
    mv -v /opt/qradar/jars/bcprov-jdk15on-1.57.jar /store/support/
  4. Stop the hostcontext service:
    systemctl stop hostcontext
  5. Restart the tomcat service:
    systemctl restart tomcat
  6. Start the hostcontext service:
    systemctl start hostcontext


Post this, you can add the managed host successfully to the JSA deployment. 

 

If the issue persists, please contact Juniper support.

Modification History

2024-09-04 : Article Created