-
Enhancement
-
Resolution: Fixed
-
P4
-
8, 11, 13
-
b08
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8228425 | 11.0.6-oracle | Sean Coffey | P4 | Resolved | Fixed | b01 |
| JDK-8230166 | 11.0.5 | Sean Coffey | P4 | Resolved | Fixed | b05 |
| JDK-8237390 | openjdk8u252 | Sean Coffey | P4 | Resolved | Fixed | b01 |
| JDK-8263820 | 8u301 | Sean Coffey | P4 | Resolved | Fixed | b01 |
It's often difficult to find out if enterprise apps are using the correct keystore or if they're even finding one at all.
the java.security.debug system related properties could be used to print out the number and type of keys found in the various keystores.
e.g.
keystore: JavaKeyStore load: private key count: 0. trusted key count: 92
keystore: JceKeyStore load: private key count: 1. trusted key count: 1. secret key count: 1
pkcs12: PKCS12KeyStore load: private key count: 1. secret key count: 0. certificate count: 1
the java.security.debug system related properties could be used to print out the number and type of keys found in the various keystores.
e.g.
keystore: JavaKeyStore load: private key count: 0. trusted key count: 92
keystore: JceKeyStore load: private key count: 1. trusted key count: 1. secret key count: 1
pkcs12: PKCS12KeyStore load: private key count: 1. secret key count: 0. certificate count: 1
- backported by
-
JDK-8228425 Enhance keystore load debug output
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-