pkiutil -import fails to load a Java Keytool generated self-signed certificate

Article discusses an issue where Java Keytool was used to create a self signed certificate for a configuration where a Sonic ESB container connects over SSL to the OE appserver, through the OE ESB adapter. The pkiutil -import failed because the private key did not exist in %DLC%/keys/requests. This article shows how to export the certificates from the JKS (Java Key Store) in format that OpenSSL can work (PKCS12) with and then import them into the OpenEdge Key store so that the appserver can be configured for SSL

  • Aug 5, 2016
  • Knowledge

Files(0)

Drop Files

    Was this article helpful?

    Related Articles

    Disclaimer

    The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

    Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.