-
Bug
-
Resolution: Fixed
-
P3
-
6
-
None
-
mustang
-
sparc
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2119540 | 5.0u1 | Seema Malkani | P3 | Resolved | Fixed | b04 |
Currently our pkcs12 implementation requires localKeyID attribute
for the private key, and the corresponding end-entity certificate,
in order to match the public/private key pair.
However, in the case of pkcs12, which has only one private key with the
associated certificate chain, we could relax this restriction, and allow
entries with null localKeyID.
Note: This request comes from Borland. See comments for details.
###@###.### 10/12/04 16:44 GMT
for the private key, and the corresponding end-entity certificate,
in order to match the public/private key pair.
However, in the case of pkcs12, which has only one private key with the
associated certificate chain, we could relax this restriction, and allow
entries with null localKeyID.
Note: This request comes from Borland. See comments for details.
###@###.### 10/12/04 16:44 GMT
- backported by
-
JDK-2119540 Allow null localKeyID attribute in pkcs12 with one private key
-
- Resolved
-