BF 7.1.2 install, validation process for PKCS certs?
Greetings,
A simple question, what process does Install Manager / Build Forge use to validate the PKCS12 cert for import as part of an install? I have a pfx that I've exported out of our windows certificate store, but Build Forge doesn't seem to like the file and indicates that it should be in PKCS12 format and readable. Oddly enough, 'openssl pkcs12 -in <cert>.p12 -info' seems to work just fine. Any thoughts? Does the cert need to have a friendly name? Should I be concerned about including the certificate chain? I'm going to try converting it to a pem and then back to pk12 to see if that makes a difference. I should easily be able to edit the pem to create a few test cases, but it would be nice to have a little more detail regarding why BF objects to the file. For reference, this is Build Forge 7.1.2.01 (iFix 1) on Windows 2003 FP1. Regards, Keir -- |
One answer
|
Just to follow up on this based on what I've learned.
The Java Key, Certificate, and KeyStore APIs are used to do the import. A simple, 'keytool -list -storetype pkcs12 -keystore <store>' can be used to validate the certificate. In my case I needed to download the Unresricted JCE policy files for IBM's JRE in order to resolve my problems. Regards, Keir -- |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.