Skip to main content

Hi, we are configuring MW with the certificate (.pfx) provided by the customer.
Currently we are getting an error that does not allow us to advance in the configuration.
We have manually uploaded the CA root in the java repository without success.


Any ideas?

Hi @ChristianP 

sometimes this may helpful

Wildcard SSL/TLS Certificate Verification Error in App10 | IFS Community

Regards
shan


Hi @ChristianP,

Please check this KB, it seems the same issue has been explained there.

/Nimesh


Hi @ChristianP,

Have you tried to reconfigure with a self-signed certificate? If not, please try and see whether you get the same error.

If you are not getting the error with a self signed certificate, then the problem should be with the certificate and you need to create one certificate containing the full chain of trust. For that you can do the following.

  1. Ask the customer to check the files they received for their CSR. There should be 2 or 3 files: the certificate file in one or 2 formats, and a bundle file containing intermediate certificates.  
  2. Using OpenSSL, combine the certificate file, the bundle file and the private key which is generated with the CSR, into one PKCS#12 file(pfx or p12 format).

Eg: openssl pkcs12 -export -out result.pfx -inkey privateKey.key -in certificate.crt -certfile bundle.crt 

Make sure to give the correct file names for the above command. Ideally, this should be done by the customer themselves, because the private key file should not be shared with others. If the bundle file is in p7b format, you need to convert it to crt format before running the above command. 

  1. Install the resulting certificate(result.pfx in above example) as a Trusted Root Certificate Authority on the Application Server host machine.
  2. Using the windows Certificate Manager, export the certificate. 
  3. Use the exported certificate in IFS Installer. 

Hope this helps!


Hi at all,

i’ve found the problem.

It was relied to the F1MAGE which is not able to read the Java certificate store so, to verify the true error, F1MAGE must be launched manually and checked (EX. certificate chain absent). Once this is done, you need to load the ROOT and sub-root certificates on the windows side. Once this is done, the certificate will be validated on the F1MAGE side and the configuration can be finished.

Thanks everyone for the ideas