Error: Could not initialize class org.bouncycastle.crypto.CryptoServicesRegistrar in VNA
Article ID: 446786
Updated On:
Products
Issue/Introduction
When attempting to add or initialize the VeloCloud Plugin in DX NetOps Virtual Network Assurance (VNA), the operation fails with the following error in the logs:
```
Could not initialize class org.bouncycastle.crypto.CryptoServicesRegistrar
```
This typically occurs during plugin deployment or after a VNA upgrade.
Environment
* DX NetOps Virtual Network Assurance (VNA) 25.4.8
* VeloCloud Plugin
* Aruba Plugin (installed concurrently)
Cause
The error is caused by a Java classloading conflict. VNA discovers duplicate Bouncy Castle cryptography libraries in the classpath. In this specific scenario, the `bc-fips-####.jar` exists in both the global Wildfly modules and the local Aruba Plugin directory, preventing the VeloCloud Plugin from initializing correctly.
Resolution
To resolve this conflict, identify and remove the duplicate library from the plugin directory.
1. Log in to the VNA server
2. Stop the Wildfly service.
systemctl stop wildfly
3. Locate duplicate Bouncy Castle JAR files. Search both the system modules and the plugins directory.
find /opt/CA/VNA/ -name "bc-fips*.jar"
4. If the JAR is found in `/opt/CA/VNA/plugins/Aruba Plugin/opencollector/repository/TIM-INF/lib/`, move it to a backup location outside of the VNA directory.
mv "/opt/CA/VNA/plugins/Aruba Plugin/opencollector/repository/TIM-INF/lib/bc-fips-2.1.2.jar" /tmp/
5. Restart the Wildfly service.
systemctl start wildfly
6. Attempt to add the VeloCloud Plugin again in the VNA UI.
Additional Information
The bc-fips-2.1.2.jar should only exist in the location below
/opt/CA/VNA/wildfly/modules/org/bouncycastle/jcajce/provider/main/bc-fips-2.1.2.jar (The correct system path)
If the issue persists, verify that no other older versions of Bouncy Castle JARs (e.g., `bcprov-*.jar`) exist in the `/opt/CA/VNA/wildfly/standalone/deployments` directory.
Feedback
