| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8291644 | 17.0.5-oracle | Raymond Gallardo | P3 | Resolved | Delivered | |
| JDK-8291645 | 11.0.7-oracle | Raymond Gallardo | P3 | Resolved | Delivered | |
| JDK-8291876 | 8u361 | Raymond Gallardo | P3 | Resolved | Fixed | b01 |
| JDK-8291646 | 8u351 | Raymond Gallardo | P3 | Resolved | Fixed | b10 |
The PKCS11 provider document makes a statement about the delayed
selection mechanism which is inconsistent with the implementation.
It claims that for Cipher, KeyAgreement, Mac, etc.:
If an application calls the initialization method multiple times
(each time with a different key, for example), the proper provider
for the given key is selected each time. In other words, a
different provider may be selected for each initialization call.
selection mechanism which is inconsistent with the implementation.
It claims that for Cipher, KeyAgreement, Mac, etc.:
If an application calls the initialization method multiple times
(each time with a different key, for example), the proper provider
for the given key is selected each time. In other words, a
different provider may be selected for each initialization call.
- backported by
-
JDK-8291644 Fix the incorrect wording about delayed provider selection in the PKCS11 documentation
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-