Oracle Wallet Manager Shows "Certificate:Empty" When Generating Wallets Using An Existing Certificate & Key
(Doc ID 1582186.1)
Last updated on SEPTEMBER 27, 2018
Applies to:Oracle Security Service - Version 18.104.22.168.0 and later
Oracle HTTP Server - Version 22.214.171.124.0 to 126.96.36.199.0 [Release Oracle11g]
Web Cache - Version 188.8.131.52.0 to 184.108.40.206.0 [Release Oracle11g]
Information in this document applies to any platform.
- A Wallet is created via openssl using the following command:
openssl pkcs12 -export -out ewallet.p12 -inkey priv.key -in cert.crt -certfile chain.crt
- When this Wallet is opened in Oracle Wallet Manager 220.127.116.11 or higher, as part of a Fusion Middleware install, the Certificate shows as "Certificate:Empty"
- The same Wallet can be:
a) imported into IE
b) Opened with OWM 10.1.0.5 ( from AS 10.1.2.3/10.1.3.5)
c) Can be dumped with orapki and the certificate shows successfully
$MIDDLEWARE_HOME/common/bin/orapki wallet display -wallet ./
d) Can be imported in FMW Control
- It also fails in 18.104.22.168 OWM, but in this case the Wallet fails to open at all.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!