IBM Support

Avoiding certificate chaining errors when loading Public Encryption/Digital Signature certificates.

Technote (troubleshooting)


This document will discuss what happens when the Intermediate or Root Certificates are missing and WPG was not able to build the complete path for the Certificate chain.


WPG will attempt to build and validate the certificate path if the bcg.build_complete_certpath= true property is set in the file. This property is set to true by default. If the path can not be verified you will receive the following errors in the bcg_router.log file: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: The certificate issued by OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US is not trusted; internal cause is: Certificate chaining error
at Source)
at Source)

Further down in the trace, you will see another error in the bcg_router..log file where WPG can not find a valid certificate: Could not get Valid encryption Certificate

Resolving the problem

The Leaf certificate for Encryption/Digital Signature must be loaded under the participant as seen in the screen shots below.

If we look at the "General" tab of the Leaf certificate for Encryption/Digital Signature, we see the "Issued to:" and the "Issued by: VeriSign Class 3 Security Server CA".

Note: The "Issued by: VeriSign Class 3 Security Server CA", is the Intermediate Certificate in the chain which will need to be extracted, if you have not already done so.

Then if we click on the same certificates "Certification Path" tab, we will see the complete path for the CA chain. As you can see in the below screen shot, the highlighted section in the chain "VeriSign Class 3 Security Server CA". This is the Intermediate certificate that must be loaded under Hub Operator" as Root/Intermediate. To insure you have the correct intermediate certificate to up load, you can extract this certificate from the Leaf certificate.

1). From this screen you can extract the Intermediate certificate, by clicking on the "View Certificate" button. This will display the Intermediate certificate "Issued by: Class Public Primary Certificate Authority" ( which is the Root Certificate).

2). To extract the Intermediate certificate, click on the "Details" tab and then click on the "Copy to File" button as seen in the screen shot above.

3). On the "Welcome to the Certificate Export Wizard" screen click on the "Next" button.

4). Select the radio button for the correct format: "DER encoded binary X.509 (.CER)" and then click "Next" button.

5). You may browse or type in path and file name for the certificate to be saved then click on the "Next" button.

6). The "Completing Certificate Export Wizard" screen is displayed. Click on the "Finish" button and you are now ready to upload the Intermediate certificate to the Hub Operator profile as Root/Intermediate as shown in the screen shot bellow.

Now you can open the Intermediate certificate you just created. You will see it was "Issued by: Class Public Primary Certificate Authority" on the general tab ( This is the Root Certificate).

To extract the Root certificate, click on the "Details" tab and follow steps 1 through 6 again to extract the Root Certificate. Once extracted you will need to upload to WPG, under profile Hub Operator as Root/Intermediate.

Here is the extracted Root Certificate. In this example, you see that the Root Certificate was "Issued by: Class 3 Public Primary Certificate Authority".

Document information

More support for: WebSphere Partner Gateway Enterprise Edition

Software version: 6.0,,,,,,,, 6.1,,,, 6.1.1,,, 6.2,,,,,,,,

Operating system(s): AIX, Linux, Solaris, Windows

Software edition: Advanced, Enterprise

Reference #: 1266207

Modified date: 13 June 2008

Translate this page: