-
Bug
-
Resolution: Fixed
-
P1
-
7u25, 8
-
b122
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8030995 | 9 | Sean Mullan | P1 | Closed | Fixed | b01 |
JDK-8031297 | 8u5 | Sean Mullan | P1 | Resolved | Fixed | b03 |
JDK-8040994 | 7u80 | Sean Mullan | P1 | Resolved | Fixed | b01 |
JDK-8040373 | 7u60 | Sean Mullan | P1 | Resolved | Fixed | b15 |
JDK-8031448 | 7u55 | Robert Mckenna | P1 | Resolved | Fixed | b04 |
JDK-8031642 | 7u51 | Mala Bankal | P2 | Resolved | Fixed | b32 |
JDK-8031421 | 1.4-pool | Mala Bankal | P2 | Closed | Not an Issue |
SHORT SUMMARY: Revocation checking via LDAP URLs ends in CNFE
DESCRIPTION:
As implemented from 7u25, revocation checks of CRLs using LDAP URLs from certificates of signed applets results in recursive calls to revocation checking and a resultant java.lang.ClassNotFoundException.
This problem existed prior to 7u25, but we are getting several reports of it now because revocation was enabled by default starting in 7u25 for signed applets and JNLP applications.
- backported by
-
JDK-8031297 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Resolved
-
-
JDK-8031448 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Resolved
-
-
JDK-8040373 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Resolved
-
-
JDK-8040994 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Resolved
-
-
JDK-8031642 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Resolved
-
-
JDK-8030995 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Closed
-
-
JDK-8031421 Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Closed
-
- relates to
-
JDK-8030828 [ Deploy Peer of JDK-8030813 ] Signed applet fails to load when CRLs are stored in an LDAP directory
-
- Closed
-