The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed. Resolved: Release in which this issue/RFE has been resolved. Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
It seems that MS CNG does not have SHA3 support. So, no changes to SunMSCAPI provider.
SunPKCS11 provider will be updated separately under a separate RFE https://bugs.openjdk.java.net/browse/JDK-8242332
10-09-2020
Current list of covered signature algorithms under this RFE:
SUN provider:
1) add impl for [SHA384/SHA512]withDSA signature,
2) add impl for [SHA3-224/SHA3-256/SHA3-384/SHA3-512]withDSA signature, and
3) the corresponding [MD]withDSAinP1363Format for the above 6 signature algorithms.
SunRsaSign provider:
1) add impl for [SHA3-224/SHA3-256/SHA3-384/SHA3-512]withRSA signatures, and
2) enhanced RSASSA-PSS signature impl to accept PSS parameters using SHA3 digests
SunEC provider:
1) add impl for [SHA3-224/SHA3-256/SHA3-384/SHA3-512]withECDSA, and
2) the corresponding [MD]withECDSAinP1363Format for these 4 signature algorithms.
06-04-2020
NIST defined SHA3 relevant algorithm oids here:
https://csrc.nist.gov/projects/computer-security-objects-register/algorithm-registration