-
Enhancement
-
Resolution: Fixed
-
P4
-
8, 9
-
b03
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8241366 | 13.0.3 | Sean Coffey | P4 | Resolved | Fixed | b01 |
JDK-8226564 | 11.0.5-oracle | Sean Coffey | P4 | Resolved | Fixed | b02 |
JDK-8228427 | 11.0.5 | Sean Coffey | P4 | Resolved | Fixed | b01 |
JDK-8235862 | openjdk8u252 | Sean Coffey | P4 | Resolved | Fixed | b01 |
JDK-8235896 | openjdk8u242 | Martin Balao Alonso | P4 | Resolved | Fixed | b05 |
JDK-8229178 | 8u241 | Sean Coffey | P4 | Resolved | Fixed | b01 |
JDK-8235038 | emb-8u241 | Sean Coffey | P4 | Resolved | Fixed | team |
Here's a recent example I worked on :
certpath: X509CertSelector.match(SN: xxx1a8ae
Issuer: OU=xxxxx CA,OU=Certification Authorities,OU=xxxxx,O=xxxx,C=US
Subject: OU=xxx CA4,OU=Certification Authorities,OU=xxxxx,O=xxxx,C=US)
certpath: X509CertSelector.match: subject key IDs don't match
Print the SKIDs! there are other examples in X509CertSelector also where we can print IDs to debug logs.
- backported by
-
JDK-8226564 Better messaging for PKIX path validation matching
-
- Resolved
-
-
JDK-8228427 Better messaging for PKIX path validation matching
-
- Resolved
-
-
JDK-8229178 Better messaging for PKIX path validation matching
-
- Resolved
-
-
JDK-8235038 Better messaging for PKIX path validation matching
-
- Resolved
-
-
JDK-8235862 Better messaging for PKIX path validation matching
-
- Resolved
-
-
JDK-8235896 Better messaging for PKIX path validation matching
-
- Resolved
-
-
JDK-8241366 Better messaging for PKIX path validation matching
-
- Resolved
-
- relates to
-
JDK-8133094 JDK 7 and orapki provider not working with JDBC using TCPS
-
- Closed
-